From: Daniel Jacobowitz <drow@false.org>
To: Markus.Grunwald@pruftechnik.com
Cc: gdb@sourceware.org
Subject: Re: gdb 6.6: incomplete backtraces ?
Date: Thu, 08 Mar 2007 15:15:00 -0000 [thread overview]
Message-ID: <20070308151547.GA4632@caradoc.them.org> (raw)
In-Reply-To: <OFEE482E12.0DBC334A-ONC1257298.0051BEA4-C1257298.0052D68D@pruftechnik.com>
On Thu, Mar 08, 2007 at 04:04:27PM +0100, Markus.Grunwald@pruftechnik.com wrote:
> Hello,
>
> while researching for another problem, I found this :
>
> gdb 6.6, compiled by myself:
> --------------------------------------------------------------------------------
> gru@CMDevLin2 >/home/gru/gdb-6.6/bin/gdb dafit_x86.bin
> GNU gdb 6.6
> (gdb) catch fork
> Catchpoint 1 (fork)
> (gdb) run
> [...]
> Catchpoint 1 (forked process 26023), 0xb7fa1410 in ?? ()
> (gdb) bt
> #0 0xb7fa1410 in ?? ()
> #1 0x00000001 in ?? ()
> #2 0x00000000 in ?? ()
> (gdb) show backtrace limit
> An upper bound on the number of backtrace levels is unlimited.
> --------------------------------------------------------------------------------
>
> Hey, that's quite short ! No matter which catchpoint is hit, I get only 3
> frames ...
What does info shared say is at that address? Anything?
It usually helps to install the Debian libc6-dbg package and configure
your GDB with --prefix=/usr. That will improve backtraces through the
system libraries.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-03-08 15:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-08 15:04 Markus.Grunwald
2007-03-08 15:15 ` Daniel Jacobowitz [this message]
2007-03-08 15:47 ` Markus.Grunwald
2007-03-08 16:06 ` Daniel Jacobowitz
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=20070308151547.GA4632@caradoc.them.org \
--to=drow@false.org \
--cc=Markus.Grunwald@pruftechnik.com \
--cc=gdb@sourceware.org \
/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