Hi Magnus,
I finally got to the bottom of this - it seems that the flags being
passed to MingW's linker were incorrect, but instead of erroring out it
decided to create a corrupt executable. Here is the command line that
was being used to link the pgsql2shp.exe executable, along with the
associate
"Magnus Hagander" <[EMAIL PROTECTED]> writes:
>> C:/msys/1.0/home/mca/pg82/REL-8~1.2BE/lib/libpq.dll -o pgsql2shp.exe
>> Info: resolving _PQntuples by linking to __imp__PQntuples (auto-import)
> This is fairly normal, and it's just info - not even a warning.
It seems pretty odd that it would only
> > > AFAICT the backtrace and server log is indicating that the
> > > crash is happening somewhere in libpq. If someone can help me
> > > figure out how to load the libpq symbols into MingW's gdb
> > > then I can get a better backtrace if required as I can
> > > reproduce this 100% of the time. Fo
On Sun, 2006-10-08 at 17:53 +0200, Magnus Hagander wrote:
> > AFAICT the backtrace and server log is indicating that the
> > crash is happening somewhere in libpq. If someone can help me
> > figure out how to load the libpq symbols into MingW's gdb
> > then I can get a better backtrace if requir
> AFAICT the backtrace and server log is indicating that the
> crash is happening somewhere in libpq. If someone can help me
> figure out how to load the libpq symbols into MingW's gdb
> then I can get a better backtrace if required as I can
> reproduce this 100% of the time. For reference, the
