From: Daniel Jacobowitz <drow@false.org>
To: Timo Sirainen <tss@iki.fi>
Cc: gdb@sources.redhat.com
Subject: Re: Linux 2.6 backtrace problems
Date: Tue, 21 Sep 2004 13:34:00 -0000 [thread overview]
Message-ID: <20040921133412.GA11077@nevyn.them.org> (raw)
In-Reply-To: <99F05BF6-0BD2-11D9-B18D-000393CC2E90@iki.fi>
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
prev parent reply other threads:[~2004-09-21 13:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-20 15:46 Timo Sirainen
2004-09-21 13:01 ` Daniel Jacobowitz
2004-09-21 13:32 ` Timo Sirainen
2004-09-21 13:34 ` Daniel Jacobowitz [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040921133412.GA11077@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=tss@iki.fi \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).