This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: Backtrace not giving meaningful info
- From: Daniel Jacobowitz <drow at mvista dot com>
- To: jlm <jsado_sc1 at earthlink dot net>
- Cc: gdb at sources dot redhat dot com
- Date: Sat, 1 Feb 2003 12:12:46 -0500
- Subject: Re: Backtrace not giving meaningful info
- References: <1044113934.7232.24.camel@PC2>
On Sat, Feb 01, 2003 at 10:38:52AM -0500, jlm wrote:
> I'm using gdb 5.3 to debug a C++ program that has been compiled with gcc
> 3.2 using the -gdwarf-2 -g3 flags. I can reliably make my program crash,
> and at that point, I want to know where my program crashed at, so I do a
> backtrace:
>
> (gdb) bt
> #0 0x4007cbd8 in ?? ()
> #1 0x4007b208 in ?? ()
> #2 0x40079560 in ?? ()
> #3 0x4008e300 in ?? ()
> #4 0x4008d44c in ?? ()
> #5 0x4008e9f7 in ?? ()
> #6 0x4006da3f in ?? ()
> #7 0x4006d25a in ?? ()
> #8 0x40082a2b in ?? ()
> #9 0x4008fc30 in ?? ()
> #10 0x4008fa6f in ?? ()
> #11 0x408d12c3 in
> Glib::SignalProxyNormal::slot0_void_callback(_GObject*, void*)
> (self=0x818d180, data=0xbfffd764) at signalproxy.cc:101
>
> I have two questions. One, why doesn't the backtrace go all the way back
> to main()? Two, what must I do in order to get some more meaningful
> information in the backtrace? The ?? doesn't help me much.
Not enough information. You need to figure out where those addresses
actually are; are they in a shared library somewhere? Try "info
shared".
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer