From: Daniel Jacobowitz <drow@mvista.com>
To: jlm <jsado_sc1@earthlink.net>
Cc: gdb@sources.redhat.com
Subject: Re: Backtrace not giving meaningful info
Date: Sat, 01 Feb 2003 17:12:00 -0000 [thread overview]
Message-ID: <20030201171246.GC29662@nevyn.them.org> (raw)
In-Reply-To: <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
next prev parent reply other threads:[~2003-02-01 17:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-01 15:43 jlm
2003-02-01 17:12 ` Daniel Jacobowitz [this message]
2003-02-02 23:15 ` jlm
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=20030201171246.GC29662@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=jsado_sc1@earthlink.net \
/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