Re: [pgadmin-hackers] stack trace

2003-06-26 Thread Jean-Michel POURE
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 t

Re: [pgadmin-hackers] stack trace

2003-06-26 Thread Andreas Pflug
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. T

Re: [pgadmin-hackers] stack trace

2003-06-26 Thread Jean-Michel POURE
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 publi

Re: [pgadmin-hackers] stack trace

2003-06-26 Thread Dave Page
> -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 Uni

Re: [pgadmin-hackers] stack trace

2003-06-25 Thread fmonkey
> 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. :-

Re: [pgadmin-hackers] stack trace

2003-06-25 Thread Andreas Pflug
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

Re: [pgadmin-hackers] stack trace

2003-06-25 Thread Dave Page
> -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 ver

Re: [pgadmin-hackers] stack trace

2003-06-25 Thread Andreas Pflug
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

Re: [pgadmin-hackers] stack trace

2003-06-25 Thread Jean-Michel POURE
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 wxG

Re: [pgadmin-hackers] stack trace

2003-06-25 Thread Adam H. Pendleton
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 --

Re: [pgadmin-hackers] stack trace

2003-06-25 Thread Andreas Pflug
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::AssignCo