Re: pgadmin 1.6.3 - segmentation fault - Mailing list pgadmin-support

From Marcin Zajączkowski
Subject Re: pgadmin 1.6.3 - segmentation fault
Date
Msg-id f5t4v9$dqj$1@sea.gmane.org
Whole thread Raw
In response to Re: pgadmin 1.6.3 - segmentation fault  (Dave Page <dpage@postgresql.org>)
Responses Re: pgadmin 1.6.3 - segmentation fault  (Dave Page <dpage@postgresql.org>)
List pgadmin-support
On 2007-06-27 09:38, Dave Page wrote:
> Marcin Zajączkowski wrote:
>> On 2007-06-19 15:27, Marcin Zajączkowski wrote:
>> (...)
>>> I already work on a snapshot and I'll let you know if a crash happens
>>> (but it can take some time, it's not 1.4.x ;) ).
>> I didn't get segmentation fault, but have something like that in gdb:
>>
>> (...)
>> [New Thread -1231369328 (LWP 6763)]
>> [Thread -1231369328 (LWP 6763) exited]
>> [New Thread -1241859184 (LWP 6768)]
>> [Thread -1241859184 (LWP 6768) exited]
>> [New Thread -1252349040 (LWP 6775)]
>> [Thread -1252349040 (LWP 6775) exited]
>> Couldn't get registers: No such process.
> 
> Did the entire app exit at that point? Just seeing threads exit isn't a
> problem in itself.

No, it hangs. gdb also freezes at "quit" and I have to kill pgadmin 
externally.

Note that it's probably not related with segmentation fault mentioned in 
the first mail of this thread.


>> I can't get stack trace and I'm not sure what is it caused by.
> 
> I assume you're running a debug build? What were you doing when this
> happened?

I have installed debuginfo packages for pgadmin, but I'm not sure is it 
enough. The problem is that I can't use any gdb command (like bt), 
because it responses with "Couldn't get registers: No such process." 
(even without debug info there is a generic stack trace).

It usually happens when I try to connect to some database.


Regards
Marcin



pgadmin-support by date:

Previous
From: Dave Page
Date:
Subject: Re: pgadmin 1.6.3 - segmentation fault
Next
From: Dave Page
Date:
Subject: Re: pgadmin 1.6.3 - segmentation fault