From: Daniel Jacobowitz <drow@false.org>
To: Bin Chen <binary.chen@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: backtrace gdb symbol error
Date: Wed, 24 Oct 2007 11:55:00 -0000 [thread overview]
Message-ID: <20071024115546.GC19251@caradoc.them.org> (raw)
In-Reply-To: <1193214024.26727.4.camel@binch-desktop>
On Wed, Oct 24, 2007 at 04:20:24PM +0800, Bin Chen wrote:
> Hi,
>
> I enounter a strange problem when i use gdb to do backtrace, I want to
> know if it is an old problem and has been fixed in newer gdb...
>
> I am doing debug from host to a target gdbserver, the frame #3's mapping
> is error, because the memory map from board shows 0x00046fd0 is not in
> the range of libstdc++.so.5, but the elf itself. And the address
> 0x41217918 in frame #13 is in the libstdc++.so.5 but the gdb can't
> recognize it. So I think the mapping is a bit disorder(but others are
> correct!!), can I print the mapping table in the gdb side(which is
> retrieved from gdbserver I think) to see if my guess is right?
Yes, "info shared".
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-10-24 11:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-24 8:20 Bin Chen
2007-10-24 9:27 ` Mark Kettenis
2007-10-24 23:40 ` Bin Chen
2007-10-24 11:55 ` Daniel Jacobowitz [this message]
2007-10-25 1:53 ` Bin Chen
2007-10-25 11:55 ` 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=20071024115546.GC19251@caradoc.them.org \
--to=drow@false.org \
--cc=binary.chen@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).