This is the mail archive of the gdb@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Backtrace not giving meaningful info


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.

Thanks.



Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]