From: Ron McCall <rmccall@sikorsky.com>
To: GDB Mailing List <gdb@sources.redhat.com>
Subject: Register setting problem
Date: Tue, 17 Sep 2002 14:12:00 -0000 [thread overview]
Message-ID: <20020917171141.A17795@sikorsky.com> (raw)
Hi,
I am using GDB from CVS on August 12th, targeted to powerpc-eabi. No
matter which general purpose register I try to set, r0 gets set instead.
For example, both "set $r3=15" and "set var $r3=15" result in r0==15 and
r3 unchanged. In case it matters, I am using target remote. With
remote debugging turned on, I can see 'P' packets go out in these cases
but always with register number 0. If I disable the 'P' packet, a 'G'
packet goes out instead but the modified value is still the first 8 hex
digits (register r0).
Has anyone else seen this?
Ron McCall
next reply other threads:[~2002-09-17 21:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-17 14:12 Ron McCall [this message]
2002-09-17 14:15 ` Daniel Jacobowitz
2002-09-17 14:23 ` Ron McCall
2002-09-17 15:03 ` Andrew Cagney
2002-09-17 15:09 ` Ron McCall
2002-09-17 15:59 ` Ron McCall
2002-09-17 16:56 ` Andrew Cagney
2002-09-17 18:11 ` Ron McCall
2002-09-18 7:24 ` Ron McCall
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=20020917171141.A17795@sikorsky.com \
--to=rmccall@sikorsky.com \
--cc=gdb@sources.redhat.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