From: 'Daniel Jacobowitz' <drow@false.org>
To: "Bloch, Jack" <jack.bloch@siemens.com>
Cc: gdb@sources.redhat.com
Subject: Re: Reading target registers
Date: Mon, 09 May 2005 21:02:00 -0000 [thread overview]
Message-ID: <20050509210228.GA14517@nevyn.them.org> (raw)
In-Reply-To: <2DA8F872430BE8469BF0F403A6103F9205CFCC@stca20aa.bocc.icn.siemens.com>
On Mon, May 09, 2005 at 12:53:20PM -0700, Bloch, Jack wrote:
> Thanks, I also waituntil the target is stopped before reading the
> registers. I get a value, just not the correct value. I noticed that I get
> the same incorrect value as the lsstack application which uses
> ptrace(PTRACE_PEEKUSER,l_pid,EIP*4,0)
> But GDB gets the correc value. I'm assuming it is something with my linking
> or which version of user I'm including. I may be way off here but any help
> is appreciated.
A couple of things:
- Always cast the arguments to ptrace. They are generally of type
"long", which may not be the same as "int".
- If you are debugging a 64-bit program you need a 64-bit GDB.
Sounds like you're on a 32-bit system though.
- Verify whether your headers are messed up. I already recommended
the use of strace for this. It can decode the arguments.
What is the incorrect value? What is the correct value?
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-05-09 21:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-09 19:53 Bloch, Jack
2005-05-09 21:02 ` 'Daniel Jacobowitz' [this message]
[not found] <2DA8F872430BE8469BF0F403A6103F9205CFCF@stca20aa.bocc.icn.siemens.com>
2005-05-09 21:22 ` 'Daniel Jacobowitz'
-- strict thread matches above, loose matches on Subject: below --
2005-05-09 19:44 Bloch, Jack
2005-05-09 19:49 ` Daniel Jacobowitz
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=20050509210228.GA14517@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=jack.bloch@siemens.com \
/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