This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: gdb 6.6: incomplete backtraces ?
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