Re: Debian Alpha (unstable) build produces bad binary - Mailing list pgadmin-support

On Monday 15 September 2003 18:12, Andreas Pflug wrote:
> Still, it's a bit unsatisfying. It should run on *all* machines, at
> least if they're Linux with recent gtk2.
> Try to put the line
> LanguageId=0
> in the file ~/.pgadmin3, this will prevent pgAdmin3 from asking for the
> language. You may still change it later from the options dialog.
> Actually, I doubt that this will help a lot, but rather crash as soon
> you open another dialog, but let's give it a try.

Here's the new output of gdb:

GNU gdb 5.3.90_2003-08-24-cvs-debian
Copyright 2003 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "alpha-linux"...(no debugging symbols found)...
(gdb) r
Starting program: /usr/bin/pgadmin3
(no debugging symbols found)...(no debugging symbols found)...(no debugging 
symbols found)...
(no debugging symbols found)...(no debugging symbols found)...(no debugging 
symbols found)...
(no debugging symbols found)...(no debugging symbols found)...(no debugging 
symbols found)...
(no debugging symbols found)...(no debugging symbols found)...(no debugging 
symbols found)...
(no debugging symbols found)...(no debugging symbols found)...(no debugging 
symbols found)...
(no debugging symbols found)...(no debugging symbols found)...(no debugging 
symbols found)...
(no debugging symbols found)...(no debugging symbols found)...(no debugging 
symbols found)...
(no debugging symbols found)...(no debugging symbols found)...(no debugging 
symbols found)...[New Thread 16384 (LWP 31597)]

(no debugging symbols found)...(no debugging symbols found)...(no debugging 
symbols found)...
(no debugging symbols found)...(no debugging symbols found)...(no debugging 
symbols found)...
(no debugging symbols found)...(no debugging symbols found)...(no debugging 
symbols found)...
(no debugging symbols found)...(no debugging symbols found)...(no debugging 
symbols found)...
(no debugging symbols found)...(no debugging symbols found)...(no debugging 
symbols found)...
(no debugging symbols found)...Cannot access memory at address 0x0
(gdb) c
Continuing.
(no debugging symbols found)...(no debugging symbols found)...(no debugging 
symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
Program received signal SIGSEGV, Segmentation fault.
0x000002000074f454 in g_type_is_a () from /usr/lib/libgobject-2.0.so.0
(gdb) bt
#0  0x000002000074f454 in g_type_is_a () from /usr/lib/libgobject-2.0.so.0
#1  0x0000020000476028 in gtk_type_new () from /usr/lib/libgtk-x11-2.0.so.0
#2  0x00000001207fe5cc in gtk_pizza_new ()
#3  0x00000001205e8040 in wxTopLevelWindowGTK::Create(wxWindow*, int, wxString 
const&, wxPoint const&, wxSize const&, long, wxString const&) ()
#4  0x00000001206544e0 in wxFrame::Create(wxWindow*, int, wxString const&, 
wxPoint const&, wxSize const&, long, wxString const&) ()
#5  0x00000001202cf400 in frmSplash::frmSplash(wxFrame*) ()
#6  0x0000000120189390 in pgAdmin3::OnInit() ()
#7  0x000000012018b7dc in wxAppConsole::CallOnInit() ()
#8  0x00000001205269b4 in wxEntry(int&, wchar_t**) ()
#9  0x0000000120526b04 in wxEntry(int&, char**) ()
#10 0x00000001201886f0 in main ()
(gdb)

Looks like it's about the same thing, only at a different spot in 
pgAdmin3::OnInit(), if I'm reading the output correctly.

Is it possible that some bug was introduced into the 2.2.4 version of gtk that 
I installed? Is there another program I could run to test gtk? I have 
everything but the kitchen sink installed on that machine -- as I said, it's 
just for playing around with mostly.

Regards,

.... Bob