> 2007/10/19, Dave Page <dpage(at)postgresql(dot)org>:
>>>>>> Bit of a long shot, but can you please move the directory
>>>>>> to somewhere outside of the appbundle and try again?
>>>>> I did, but nothing changed.
>>>> In which case I can only think that you must have a library on your
>>>> system that for some reason the pgAdmin build doesn't like. That
>>>> /shouldn't/ happen of course but I'm not sure what else it could be
>>>> given that the same appbundle works for others.
>>>> Are you able to build from source?
>>> I tried to build pgAdmin from source, but the same thing happened.
>> In that case I'm afraid I have no idea. Anyone else?
> Maybe it will make sense if i build all components with
> --enable-debug? I'm not much of a programmer, but if you give me some
> clues how to collect crash data and debug info, I can do this.
We can certainly try that. If you build a debug bundle (make the
components with the debug flag, and instead of 'make install' run
pkg/mac/debug-bundle.sh), you should then be able to run it under GDB
with something like:
and then use 'run' to start it. When it crashes, lets start by using
'bt' to get a backtrace and take it from there (yes, it'll look like the
original one from the crash report, but they're often misleading when
generated from release builds).
In response to
pgadmin-support by date
|Next:||From: Jyrki Wahlstedt||Date: 2007-10-19 13:00:31|
|Subject: Re: pgAdmin 1.8RC1 - failed to launch on Mac OS X|
|Previous:||From: Dave Page||Date: 2007-10-19 10:35:45|
|Subject: Re: [pgadmin-support] copy empty table crash|