Re: pgadmin3-1.6.0 - Segmentation Fault (core dumped)

Dhanaraj M wrote:
>
>> I'm confused - you said this happens when you close the query window,
>> but the stack trace shows frmQuery::OnChangeConnection(wxCommandEvent)
>>
>> >> Do you want to save-> NO
>> >> Segmentation Fault (core dumped)
>>
>> Is that the right core file? If so, can you detail the exact steps you
>> take to get to the crash, because I can't provoke a crash even playing
>> with the connection select dialogue (though I am running on
>> wxGTK/Linux rather than wxGTK/Solaris).
>
> Yes. I re-checked. I sent the right file.
>
> STEPS: I open pgadmin. Connect to my local machine. Select the DB. Goto
> query tool. close the tool. Pgadmin aborts.
>
> Whenever I close the query tool,  I see the core dump. (Same problem -
> even when I open the query tool and close or execute quries and close)
> This is there both in 1.6.0 and 1.6.1.

No, certainly can't reproduce this. I just tried installing Solaris 10
on VMware so I could test this, but unfortunately it's having some
serious stability issues so I'm not sure there's much debugging I can do
easily :-(

>> One other thing - are you building with --enable-debug? That might
>> help get more meaningful debug output.
>
>
> I am currently working on this. I will send them ASAP.

Thanks. I really don't understand the traces you've sent so far - they
all include functions in dlgSelectConnection which would never be called
following the steps you give above unless there is something *very*
wrong with your build.

>>> 2. When I right click on a table and select view data, it aborts. The
>>> stack trace is here.
>>
>>
>> I cannot reproduce this either. Do you have permission to view that
>> particular table? Does it only occur with specific tables?
>
> This behaviour is not consistent. It is not related to the table. This
> problem may occur only certain times (not always) for the same set of
> steps.
> This problem is only with 1.6. 1 and not in 1.6.0.
>
> +++++++++++++++++++++++++++++++++++++++++
> -
> I noticed one more in-consistent problem in the query tool. Sometimes
> there is no results displayed after executing the query.

Is your libpq built with --enable-thread-safety?

Regards, Dave.