Re: Segfault

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Oliver Elphick <olly(at)lfix(dot)co(dot)uk>
Cc: pgsql-odbc(at)postgresql(dot)org
Subject: Re: Segfault
Date: 2003-10-21 22:57:16
Message-ID: 6838.1066777036@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-odbc

Oliver Elphick <olly(at)lfix(dot)co(dot)uk> writes:
> I have not been able to trace the program because I haven't yet worked
> out how to set breakpoints in a module loaded after the run command in
> gdb.

Set a breakpoint somewhere after the module will be loaded. Once the
module has been loaded, you can tell gdb about it with

gdb> sharedlibrary path-to-.so-file

Then you'll be able to set a breakpoint in the shared library.
(An annoyance here is that you can't restart the program from scratch
without losing this work and having to redo it. Grumble.)

At least, that works for me on HP-UX. I assume it's the same on all
gdb platforms ...

regards, tom lane

In response to

  • Segfault at 2003-10-21 22:16:42 from Oliver Elphick

Browse pgsql-odbc by date

  From Date Subject
Next Message Dave Page 2003-10-23 07:56:49 psqlODBC 07.03.0200 Released
Previous Message Oliver Elphick 2003-10-21 22:16:42 Segfault