Thread: pga3 segmentation fault

pga3 segmentation fault

From
"Adam H. Pendleton"
Date:
When running pgAdmin3 on RedHat 9, I get the following segmentation
fault when selecting Tools->Query Builder:

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1080417088 (LWP 27644)]
0x083cc1a2 in wxWindowBase::SetSize(int, int, int, int, int) (this=0x0,
x=0, y=0, width=750, height=277, sizeFlags=3) at window.h:184

ahp


Re: pga3 segmentation fault

From
"Dave Page"
Date:

> -----Original Message-----
> From: Adam H. Pendleton [mailto:fmonkey@fmonkey.net]
> Sent: 14 May 2003 19:09
> To: pgadmin-hackers@postgresql.org
> Subject: [pgadmin-hackers] pga3 segmentation fault
>
>
> When running pgAdmin3 on RedHat 9, I get the following segmentation
> fault when selecting Tools->Query Builder:
>
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 1080417088 (LWP 27644)]
> 0x083cc1a2 in wxWindowBase::SetSize(int, int, int, int, int)
> (this=0x0,
> x=0, y=0, width=750, height=277, sizeFlags=3) at window.h:184

Is this your own build from CVS or a snapshot?

Regards, Dave.

Re: pga3 segmentation fault

From
"Dave Page"
Date:

> -----Original Message-----
> From: Adam H. Pendleton [mailto:fmonkey@fmonkey.net]
> Sent: 14 May 2003 19:09
> To: pgadmin-hackers@postgresql.org
> Subject: [pgadmin-hackers] pga3 segmentation fault
>
>
> When running pgAdmin3 on RedHat 9, I get the following segmentation
> fault when selecting Tools->Query Builder:
>
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 1080417088 (LWP 27644)]
> 0x083cc1a2 in wxWindowBase::SetSize(int, int, int, int, int)
> (this=0x0,
> x=0, y=0, width=750, height=277, sizeFlags=3) at window.h:184

Dave Page wrote:

>Is this your own build from CVS or a snapshot?
>
>
This is a CVS build.

Hmm, not sure then. I don't have Redhat to test unfortunately. Looks
like it's crashing in wx though, at a guess because parameter one is 0.

Andreas, do you have any ideas? I'm still a C++ newbie and have trouble
with my own segfaults, never mind those I can't test myself! :-)

Regards, Dave.

Re: pga3 segmentation fault

From
efesar
Date:
> Hmm, not sure then. I don't have Redhat to test unfortunately. Looks
> like it's crashing in wx though, at a guess because parameter one is 0.
>
> Andreas, do you have any ideas? I'm still a C++ newbie and have trouble
> with my own segfaults, never mind those I can't test myself! :-)

I don't have a clue on that one. It might be fixed in my next update. It's a
pretty hefty update, lots of changes. I would recommend that nobody changes
Query Builder code in CVS (since the changes are so extensive) until I'm
done. Just avoid it for now as "pre-alpha" on some systems? Or if someone
has a fix, let me know and I'll fix it in my sandbox. Anyway, just a
thought.

-Keith

> -----Original Message-----
> From: pgadmin-hackers-owner@postgresql.org
> [mailto:pgadmin-hackers-owner@postgresql.org]On Behalf Of Dave Page
> Sent: Wednesday, May 14, 2003 2:04 PM
> To: Adam H. Pendleton; pgadmin-hackers@postgresql.org
> Subject: Re: [pgadmin-hackers] pga3 segmentation fault
>
>
>
>
> > -----Original Message-----
> > From: Adam H. Pendleton [mailto:fmonkey@fmonkey.net]
> > Sent: 14 May 2003 19:09
> > To: pgadmin-hackers@postgresql.org
> > Subject: [pgadmin-hackers] pga3 segmentation fault
> >
> >
> > When running pgAdmin3 on RedHat 9, I get the following segmentation
> > fault when selecting Tools->Query Builder:
> >
> > Program received signal SIGSEGV, Segmentation fault.
> > [Switching to Thread 1080417088 (LWP 27644)]
> > 0x083cc1a2 in wxWindowBase::SetSize(int, int, int, int, int)
> > (this=0x0,
> > x=0, y=0, width=750, height=277, sizeFlags=3) at window.h:184
>
> Dave Page wrote:
>
> >Is this your own build from CVS or a snapshot?
> >
> >
> This is a CVS build.
>
> Hmm, not sure then. I don't have Redhat to test unfortunately. Looks
> like it's crashing in wx though, at a guess because parameter one is 0.
>
> Andreas, do you have any ideas? I'm still a C++ newbie and have trouble
> with my own segfaults, never mind those I can't test myself! :-)
>
> Regards, Dave.
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo@postgresql.org so that your
> message can get through to the mailing list cleanly
>
>



Re: pga3 segmentation fault

From
Andreas Pflug
Date:
efesar wrote:

>I don't have a clue on that one. It might be fixed in my next update. It's a
>pretty hefty update, lots of changes. I would recommend that nobody changes
>Query Builder code in CVS (since the changes are so extensive) until I'm
>done. Just avoid it for now as "pre-alpha" on some systems? Or if someone
>has a fix, let me know and I'll fix it in my sandbox. Anyway, just a
>thought.
>
>
That seems to be the old bug, known in BUGS.txt. Just launched gvd, and
indeed it's the callstack situation described there. Didn't read the wx
doc what wxLayoutAlgorithm is, maybe Keith knows more.

Regards,
Andreas



Re: pga3 segmentation fault

From
"Dave Page"
Date:

> -----Original Message-----
> From: efesar [mailto:efesar@nmia.com]
> Sent: 14 May 2003 21:18
> To: Dave Page; Adam H. Pendleton; pgadmin-hackers@postgresql.org
> Subject: RE: [pgadmin-hackers] pga3 segmentation fault
>
>
>
> > Hmm, not sure then. I don't have Redhat to test
> unfortunately. Looks
> > like it's crashing in wx though, at a guess because
> parameter one is
> > 0.
> >
> > Andreas, do you have any ideas? I'm still a C++ newbie and have
> > trouble with my own segfaults, never mind those I can't
> test myself!
> > :-)
>
> I don't have a clue on that one. It might be fixed in my next
> update. It's a pretty hefty update, lots of changes. I would
> recommend that nobody changes Query Builder code in CVS
> (since the changes are so extensive) until I'm done. Just
> avoid it for now as "pre-alpha" on some systems? Or if
> someone has a fix, let me know and I'll fix it in my sandbox.
> Anyway, just a thought.

Sorry Keith - you lurk so quietly most of the time that I forget you're
still working on things :-). Any eta on that patch and some hints as to
what it does?

On the project management side of things, do my suggestions to Adam
clash with work you've done/are doing (other than the fact it's the same
bit of the system)? If so, perhaps Adam would be better off helping
Andreas with the object dialogues...

You'll have to give me a bit of leeway here guys - pgAdmin never had so
many people working on it before (normally it was just me and maybe one
other person) :-). Any toe-treading is purely acceidental, so if I screw
up please let me know and don't take it to heart!! Trying to organise a
group of volunteers is a whole heap different from paid staff....

Regards, Dave.