From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-30003-listarch-gdb=sources.redhat.com@sourceware.org>
Received: (qmail 21518 invoked by alias); 24 Oct 2007 23:40:28 -0000
Received: (qmail 21497 invoked by uid 22791); 24 Oct 2007 23:40:27 -0000
X-Spam-Check-By: sourceware.org
Received: from nf-out-0910.google.com (HELO nf-out-0910.google.com) (64.233.182.190)     by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 24 Oct 2007 23:40:25 +0000
Received: by nf-out-0910.google.com with SMTP id b11so342806nfh         for <gdb@sourceware.org>; Wed, 24 Oct 2007 16:40:22 -0700 (PDT)
Received: by 10.86.86.12 with SMTP id j12mr843653fgb.1193269222515;         Wed, 24 Oct 2007 16:40:22 -0700 (PDT)
Received: by 10.86.61.17 with HTTP; Wed, 24 Oct 2007 16:40:22 -0700 (PDT)
Message-ID: <5800c1cc0710241640u3ddabb91me4bbe1b2a6d29597@mail.gmail.com>
Date: Wed, 24 Oct 2007 23:40:00 -0000
From: "Bin Chen" <binary.chen@gmail.com>
To: "Mark Kettenis" <mark.kettenis@xs4all.nl>
Subject: Re: backtrace gdb symbol error
Cc: gdb@sourceware.org
In-Reply-To: <200710240927.l9O9RbBo028421@brahms.sibelius.xs4all.nl>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <1193214024.26727.4.camel@binch-desktop> 	 <200710240927.l9O9RbBo028421@brahms.sibelius.xs4all.nl>
X-IsSubscribed: yes
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/msg00223.txt.bz2

On 10/24/07, Mark Kettenis <mark.kettenis@xs4all.nl> wrote:
> > 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.

No, the library is not stripped, I am sure. Even it is stripped, the
map should be right.