From: "Srinivas Murthy" <codevana@gmail.com>
To: gdb@sourceware.org
Subject: x86_64 gdb and objdump
Date: Mon, 02 Jul 2007 19:14:00 -0000 [thread overview]
Message-ID: <df1bdeb10707021214r566c406ev82795c216b3be276@mail.gmail.com> (raw)
From a core dump file, I see that with gdb I get a "Cannot access
memory at address xx" msg but using objdump, I can see the contents of
the memory location on the core file.
Any ideas what is going wrong?
Thanks.
# gdb test core_dir/core.test.30235
GNU gdb 6.6
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "x86_64-unknown-linux-gnu"...
Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `./test'.
Program terminated with signal 11, Segmentation fault.
#0 0x00000000004004f5 in bar () at test.c:10
10 test.c: No such file or directory.
in test.c
(gdb) bt
#0 0x00000000004004f5 in bar () at test.c:10
Cannot access memory at address 0x7fbfffee98
However, objdump shows that there is some valid content at the location:
# objdump -D /tmp/core.test.30235 |less |grep 7fbfffee98
7fbfffe95f: 00 08 add %cl,(%rax)
next reply other threads:[~2007-07-02 19:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-02 19:14 Srinivas Murthy [this message]
2007-07-02 19:23 ` Daniel Jacobowitz
2007-07-02 20:39 ` Srinivas Murthy
2007-07-02 21:03 ` Daniel Jacobowitz
2007-07-02 23:17 ` Srinivas Murthy
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=df1bdeb10707021214r566c406ev82795c216b3be276@mail.gmail.com \
--to=codevana@gmail.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