From: Duane Ellis <duane_ellis@franklin.com>
To: insight@sources.redhat.com
Subject: Re: Adding Registers
Date: Thu, 14 Feb 2002 07:03:00 -0000 [thread overview]
Message-ID: <200202141503.KAA18618@mercury.franklin.com> (raw)
In-Reply-To: <3c948824.1980.0@esatclear.ie> (mckennad@esatclear.ie)
david> Andrew refers to the internal number of each register. I am
dealing with a memory mapped register and as such it has no
number, how is this dealt with in the functions.
You are thinking like "r0" "r1" and such.
What number would you then apply to the PC, or the STACK pointer?
Numbers are some what arbitrary. Think of it as "register id" ID
numbers 0..15 mean registers 0..15, id 16 is PC, 17 is stack, 18 is
flags register, 19 is this, and 20 is that, and 21 is _other_
david> I have gotten as far as
Good, next step is to fire up the debugger, and set a break point at
that specific function. Run GDB, and use the GDB commands to modify or
change a register.
BANG - you hit the break point, and you step into the function keep
stepping till you find the function you need tomodify. Exit GDB, and
hack away.
This method sure beats digging through source... and un-winding macros.
-Duane.
next prev parent reply other threads:[~2002-02-14 15:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-14 4:32 David Mc Kenna
2002-02-14 7:03 ` Duane Ellis [this message]
2002-02-14 7:39 ` Andrew Cagney
-- strict thread matches above, loose matches on Subject: below --
2002-02-13 3:40 David Mc Kenna
2002-02-13 6:49 ` Duane Ellis
2002-02-13 10:05 ` Andrew Cagney
2002-02-12 6:27 David Mc Kenna
2002-02-12 7:17 ` Duane Ellis
2002-02-12 8:58 ` Keith Seitz
2002-02-12 19:26 ` Andrew Cagney
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=200202141503.KAA18618@mercury.franklin.com \
--to=duane_ellis@franklin.com \
--cc=insight@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).