From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-32263-listarch-gdb=sources.redhat.com@sourceware.org>
Received: (qmail 8132 invoked by alias); 27 Jun 2008 17:57:21 -0000
Received: (qmail 8122 invoked by uid 22791); 27 Jun 2008 17:57:20 -0000
X-Spam-Check-By: sourceware.org
Received: from bluesmobile.specifix.com (HELO bluesmobile.specifix.com) (216.129.118.140)     by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 27 Jun 2008 17:57:03 +0000
Received: from [127.0.0.1] (bluesmobile.specifix.com [216.129.118.140]) 	by bluesmobile.specifix.com (Postfix) with ESMTP id A56A03BB4A; 	Fri, 27 Jun 2008 10:57:01 -0700 (PDT)
Subject: Re: Increasing backtrace entries
From: Michael Snyder <msnyder@specifix.com>
To: JobHunts02@aol.com
Cc: gdb@sourceware.org
In-Reply-To: <bd4.34247d07.3595dcfd@aol.com>
References: <bd4.34247d07.3595dcfd@aol.com>
Content-Type: text/plain
Date: Fri, 27 Jun 2008 17:57:00 -0000
Message-Id: <1214589421.3601.1435.camel@localhost.localdomain>
Mime-Version: 1.0
X-Mailer: Evolution 2.10.3 (2.10.3-7.fc7)
Content-Transfer-Encoding: 7bit
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: 2008-06/txt/msg00300.txt.bz2

On Fri, 2008-06-27 at 02:04 -0400, JobHunts02@aol.com wrote:
> In a message dated 6/26/2008 11:27:23 AM Pacific  Daylight Time, 
> msnyder@specifix.com writes:
> > > > warning: exec file  is newer than core file.
> > > > Cannot access memory at  address  0x6d61706c
> > > > (gdb) bt
> > > > #0  0x1003cc60 in  wsrFind  (
> > > > reg_p=0x30284d9e <Address 0x30284d9e out  of  bounds>, rxc=-1)
> > > > at lwc.c:4024
> > > >  Cannot access memory  at address 0x30284d84
> > > > (gdb)
> >  > 
> > > Apparently the core file does not match the executable and/or  debugging
> > > info you have.  If that is the case then  nothing can be done about that,
> > > except by manually decoding the  frames.
> >
> > Yes, the appearance is that either (a) you have  recompiled
> > the executable since the corefile was generated, or (b)  it's
> > the wrong executable, in which case finding the right one
> >  will solve your problem.  
> 
> 
> I can assure you:
>  
> (a) The executable was not recompiled after the corefile was generated.  and
> (b) The executable is the same one that lead to the generation of the  
> corefile.
>  
> Any other explanations?  I am running Linux 2.6.10 on PowerPC.and was  using 
> gdb 6.8.  I have seen the same behavior using older versions of gdb  too.

None at all.  I was just noting this message gdb:

  warning: exec file  is newer than core file.

which suggests that the date stamp on the object 
file is more recent than the one on the corefile.

I have no other thoughts on the matter.