This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: backtrace gdb symbol error
- From: Mark Kettenis <mark dot kettenis at xs4all dot nl>
- To: binary dot chen at gmail dot com
- Cc: gdb at sourceware dot org
- Date: Wed, 24 Oct 2007 11:27:37 +0200 (CEST)
- Subject: Re: backtrace gdb symbol error
- References: <1193214024.26727.4.camel@binch-desktop>
> From: Bin Chen <binary.chen@gmail.com>
> Date: Wed, 24 Oct 2007 16:20:24 +0800
>
> 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?
More likely that your libstdc++ library has to much information
stripped out of it.
Mark