This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: Linux 2.6 backtrace problems
On Tue, Sep 21, 2004 at 04:31:53PM +0300, Timo Sirainen wrote:
> On 21.9.2004, at 16:01, Daniel Jacobowitz wrote:
>
> >>#0 0xb7ebdee9 in raise () from /lib/tls/libc.so.6
> >>#1 0xb7fcbedc in ?? () from /lib/tls/libc.so.6
> ..
> >You are using a C library which was built without frame pointers and
> >shipped without debug info. If this is a Debian system, install the
> >Debian packages of gdb and libc6-dbg and let us know if it's still
> >there.
>
> It does seem to work, but I'm not really happy with that solution
> either. I didn't need to use libc6-dbg with 2.4 kernel and using it
> seems to be a bit of a pain.
>
> It's a bit strange that raise(SIGABRT) works, kill(getpid(), SIGABRT)
> works, etc. It's only abort() that's the problem. But if it's only a
> libc problem I'll submit a Debian bugreport.
I'm not talking about using LD_LIBRARY_PATH=/usr/lib/debug. You should
be able to just install the libc6-dbg package and debug the same copy
of glibc you were using before. Backtraces should "magically" begin to
work.
If that does not happen, please do submit a Debian bug report.
--
Daniel Jacobowitz