Raphaël Enrici wrote:
> Krzysztof Kajkowski wrote:
>
>> W liście z śro, 12-05-2004, godz. 12:17, blacknoz@club-internet.fr
>> pisze:
>>
>>
>>> So, it seems that it still occurs... I'll try to reproduce this
>>> tonight.
>>> Maybe a backtrace of the process would help.
>>> If you have some time, launch pgadmin3 in gdb like this:
>>> gdb pgadmin3
>>> then type "run"
>>> Reproduce the crash and when it segfault, type "bt" in the gdb
>>> window and send the output.
>>>
>>
>>
>> Here it goes:
>>
>> #0 0x08501420 in wxWindowBase::GetId ()
>> #1 0x08448b24 in gtk_window_event_event_callback ()
>> #2 0x4024c864 in _gtk_marshal_B
>>
>>
> ...
> to me it's another bug... It's the one related to this:
> open the sql window, modify it, don't launch and just quit it.
> pgA3 will ask if you want to save or not, if you click on "no" it
> crashes.
> The segfault is not due to any kind of dropped object.
> Can you confirm this ?
> Andreas, what is the status of this one ? I can't remember...
That mentioned problem was about objects deleted outside of the object
tree (e.g. from query window or other workstation), so that the object
wasn't valid any more when refresh is triggered.
> When it was on the top of the stack, I tried looking at it and it
> seems pgA3 did not crashed while traced... It make me thought some
> object was unproperly destroyed too fast which effectively made the
> "GetId" fail...
AFAICS from a quick glance at wx source the segv happens after the page
contents is destroyed, however this must be debugged.
Regards,
Andreas