From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-29971-listarch-gdb=sources.redhat.com@sourceware.org>
Received: (qmail 6620 invoked by alias); 24 Oct 2007 09:27:48 -0000
Received: (qmail 6609 invoked by uid 22791); 24 Oct 2007 09:27:47 -0000
X-Spam-Check-By: sourceware.org
Received: from sibelius.xs4all.nl (HELO brahms.sibelius.xs4all.nl) (82.92.89.47)     by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 24 Oct 2007 09:27:42 +0000
Received: from brahms.sibelius.xs4all.nl (kettenis@localhost.sibelius.xs4all.nl [127.0.0.1]) 	by brahms.sibelius.xs4all.nl (8.14.1/8.14.0) with ESMTP id l9O9RbMV000396; 	Wed, 24 Oct 2007 11:27:37 +0200 (CEST)
Received: (from kettenis@localhost) 	by brahms.sibelius.xs4all.nl (8.14.1/8.14.1/Submit) id l9O9RbBo028421; 	Wed, 24 Oct 2007 11:27:37 +0200 (CEST)
Date: Wed, 24 Oct 2007 09:27:00 -0000
Message-Id: <200710240927.l9O9RbBo028421@brahms.sibelius.xs4all.nl>
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: binary.chen@gmail.com
CC: gdb@sourceware.org
In-reply-to: <1193214024.26727.4.camel@binch-desktop> (message from Bin Chen 	on Wed, 24 Oct 2007 16:20:24 +0800)
Subject: Re: backtrace gdb symbol error
References:  <1193214024.26727.4.camel@binch-desktop>
Mailing-List: contact gdb-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb.sourceware.org>
List-Subscribe: <mailto:gdb-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb/>
List-Post: <mailto:gdb@sourceware.org>
List-Help: <mailto:gdb-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-owner@sourceware.org
X-SW-Source: 2007-10/txt/msg00191.txt.bz2

> 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