Re: [pgadmin-hackers] stack trace
On Thursday 26 June 2003 00:43, Andreas Pflug wrote: > Maybe this issue is a reason to upgrade. Why no strore in CVS a small document with wxWindows library requirements, so that anyone can use the same. I see no objection in upgrading regularly the RPM packages, the only point is that we need to be informed... Cheers, Jean-Michel ---(end of broadcast)--- TIP 8: explain analyze is your friend
Re: [pgadmin-hackers] stack trace
Jean-Michel POURE wrote: On Wednesday 25 June 2003 23:25, Dave Page wrote: I thought we had agreed to stick to 2003-06-07 unless a specific reason for upgrading cropped up? I agree we all need to stick to the same wxGTK version. From now on, I will be rebuilding wxGTK everyday from CVS. The packages wron't be publised. No don't do this! I tested yesterday, and had to go back to 18th to get a workable system with gtk2. The current head is marked as "broken except windows", there's heavy reconstruction work underway. Regards, Andreas ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
Re: [pgadmin-hackers] stack trace
On Wednesday 25 June 2003 23:25, Dave Page wrote: > I thought we had agreed to stick to 2003-06-07 unless a specific reason > for upgrading cropped up? I agree we all need to stick to the same wxGTK version. >From now on, I will be rebuilding wxGTK everyday from CVS. The packages wron't be publised. When needed, we should be able to upgrade all RPM packages. Cheers, Jean-Michel ---(end of broadcast)--- TIP 8: explain analyze is your friend
Re: [pgadmin-hackers] stack trace
> -Original Message- > From: Andreas Pflug [mailto:[EMAIL PROTECTED] > Sent: 25 June 2003 23:44 > To: Dave Page > Cc: [EMAIL PROTECTED]; Reinhard Max; [EMAIL PROTECTED] > Subject: Re: [pgadmin-hackers] stack trace > > We still have an open wxWindows bug with Unicode, and maybe Adam has > another from QB. > Maybe this issue is a reason to upgrade. Yes, if it helps. If someone can try it and report back, then if it makes a difference we should *all* upgrade. Regards, Dave. ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [pgadmin-hackers] stack trace
> We still have an open wxWindows bug with Unicode, and maybe Adam has > another from QB. > Maybe this issue is a reason to upgrade. > I'm pretty sure that the bugs with QB are our own. Whichever way we choose to go, please let me know so I can settle on a wxWindows tree and get it over with. :-) ahp ---(end of broadcast)--- TIP 8: explain analyze is your friend
Re: [pgadmin-hackers] stack trace
Dave Page wrote: -Original Message- From: Jean-Michel POURE [mailto:[EMAIL PROTECTED] Sent: 25 June 2003 19:49 To: Andreas Pflug; Reinhard Max Cc: [EMAIL PROTECTED] Subject: Re: [pgadmin-hackers] stack trace Andreas, I thought the latest recommanded version was 2003-06-07. All RPMs are based on it. Shall I upgrade them all? This can be done within hours if you require it. I thought we had agreed to stick to 2003-06-07 unless a specific reason for upgrading cropped up? I don't want us to be chasing new wxWindows bugs this close to release unless there's a damn good reason. I'm nervous enough using CVS code... We still have an open wxWindows bug with Unicode, and maybe Adam has another from QB. Maybe this issue is a reason to upgrade. Regards, Andreas ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [pgadmin-hackers] stack trace
> -Original Message- > From: Jean-Michel POURE [mailto:[EMAIL PROTECTED] > Sent: 25 June 2003 19:49 > To: Andreas Pflug; Reinhard Max > Cc: [EMAIL PROTECTED] > Subject: Re: [pgadmin-hackers] stack trace > > > Andreas, I thought the latest recommanded version was > 2003-06-07. All RPMs are based on it. Shall I upgrade them > all? This can be done within > hours if you require it. I thought we had agreed to stick to 2003-06-07 unless a specific reason for upgrading cropped up? I don't want us to be chasing new wxWindows bugs this close to release unless there's a damn good reason. I'm nervous enough using CVS code... Regards, Dave. ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [pgadmin-hackers] stack trace
Jean-Michel POURE wrote: Andreas, I thought the latest recommanded version was 2003-06-07. All RPMs are based on it. Shall I upgrade them all? This can be done within hours if you require it. Please try it. From time to time, I update my wx, and since there's been a change just in the region that crashes this might include a required fix. Regards, Andreas ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
Re: [pgadmin-hackers] stack trace
On Wednesday 25 June 2003 19:23, Andreas Pflug wrote: > I got a bit deeper into this and found that things happen while global > wxWindows vars are initialized. From wxString::AllocBeforeWrite being in > string.h I can see that your're using an older wxWindows version, which > is it? It is our wxGTK 2.5 cvs 20030607 version installed from RPM. From http://www.pgadmin.org/snapshots/linux/suse82/wxGTK2 > The latest version that is usable is June 18 (just checked), later > versions are broken for non-win32. So please use cvs update -D > 2003-06-18 to obtain a wx version. Andreas, I thought the latest recommanded version was 2003-06-07. All RPMs are based on it. Shall I upgrade them all? This can be done within hours if you require it. Cheers, Jean-Michel ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [pgadmin-hackers] stack trace
Andreas Pflug wrote: The latest version that is usable is June 18 (just checked), later versions are broken for non-win32. So please use cvs update -D 2003-06-18 to obtain a wx version. Or cvs co -D 2003-06-18 wxWindows if you need to obtain a fresh tree. :-) ahp ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [pgadmin-hackers] stack trace
Reinhard Max wrote: Hi, here comes the stack trace from the segfault I got when I tried to start pgAdmin on SuSE Linux 8.2 for the first time: #0 wxString::AllocBeforeWrite(unsigned) (this=0x874d78c, nLen=4) at include/wx/string.h:188 #1 0x0001 in ?? () #2 0x0845709f in wxString::AssignCopy(unsigned, wchar_t const*) (this=0x874d78c, nSrcLen=4, pszSrcData=0x874d78c)at src/common/string.cpp:548 #3 0x08457270 in wxString::operator=(wchar_t const*) (this=0x874d78c, psz=0x4) at include/wx/wxchar.h:669 #4 0x084dd48a in wxProtoInfo (this=0x4, name=0x0, serv=0x0, info=0x0) at src/common/protocol.cpp:44 #5 0x084e0a9c in __static_initialization_and_destruction_0 (__initialize_p=0, __priority=65535)at src/common/sckfile.cpp:32 #6 0x084e0b9a in _GLOBAL__I__Z27wxConstructorForwxFileProtov () at src/common/sckfile.cpp:33 #7 0x084ead25 in __do_global_ctors_aux () #8 0x0814f971 in _init () #9 0x084eac9c in __libc_csu_init () at elf-init.c:60 #10 0x40768838 in __libc_start_main () from /lib/libc.so.6 I got a bit deeper into this and found that things happen while global wxWindows vars are initialized. From wxString::AllocBeforeWrite being in string.h I can see that your're using an older wxWindows version, which is it? The latest version that is usable is June 18 (just checked), later versions are broken for non-win32. So please use cvs update -D 2003-06-18 to obtain a wx version. Regards, Andreas ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
