On Mon, 13 Feb 2006, Tom Lane wrote:
> Andrew Klosterman <[EMAIL PROTECTED]> writes:
> > (gdb) bt
> > #0 0x401c3851 in kill () from /lib/libc.so.6
> > #1 0x40139dd5 in EF_Abort () from /usr/lib/libefence.so.0
> > #2 0x40139823 in memalign () from /usr/lib/libefence.so.0
> > #3 0x401399ad in malloc () from /usr/lib/libefence.so.0
> > #4 0x40139a10 in calloc () from /usr/lib/libefence.so.0
> > #5 0x404a182f in krb5_set_default_tgs_ktypes () from /usr/lib/libkrb5.so.3
> > #6 0x402c8b3f in ?? () from /usr/lib/libpq.so.4
> > #7 0x402ded88 in ?? () from /usr/lib/libpq.so.4
> > #8 0x00000000 in ?? ()
>
> Any chance of doing this with debug symbols? libpq does not call
> krb5_set_default_tgs_ktypes directly, so I don't think I believe the
> above backtrace. gdb is easily misled without debug symbols :-(
>
> I'm not sure if Debian does things the way Red Hat does, but on RH
> there are separate "debuginfo" RPMs corresponding to each regular
> RPM --- if you install the ones matching your libpq and libkrb5
> RPMs you should be able to get better info.
>
> regards, tom lane
I thought about that and did some quick checks of how to get debug symbols
in libraries on Debian. I didn't come up with anything right away. I'll
poke around and see what I can come up with.
--Andrew J. Klosterman
[EMAIL PROTECTED]
---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
