From: JobHunts02@aol.com
To: gdb@sourceware.org
Subject: Re: Increasing backtrace entries
Date: Fri, 27 Jun 2008 06:05:00 -0000 [thread overview]
Message-ID: <bd4.34247d07.3595dcfd@aol.com> (raw)
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.
**************Gas prices getting you down? Search AOL Autos for
fuel-efficient used cars. (http://autos.aol.com/used?ncid=aolaut00050000000007)
next reply other threads:[~2008-06-27 6:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-27 6:05 JobHunts02 [this message]
2008-06-27 17:57 ` Michael Snyder
-- strict thread matches above, loose matches on Subject: below --
2008-06-26 8:00 JobHunts02
2008-06-26 9:15 ` Andreas Schwab
2008-06-26 18:26 ` Michael Snyder
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=bd4.34247d07.3595dcfd@aol.com \
--to=jobhunts02@aol.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