* Tom Lane (tgl@sss.pgh.pa.us) wrote:
> Andrew Klosterman <andrew5@ece.cmu.edu> 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 ?? ()
>=20
> 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 :-(
Hrmpf, I missed this bug-on-Debian report. I'll go check the archive
for the rest.
> 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.
We do have debugging .debs- for some things. We don't have them for
everything and unfortunately we don't yet have them for Postgres. I'll
talk to Martin about building some though so that in the future it's
easier to debug these problems.
Thanks,
Stephen