From: Richard Earnshaw <rearnsha@arm.com>
To: Hornung Peter <peter_hornung@siemens.com>
Cc: "'gdb-patches@sources.redhat.com'"
<gdb-patches@sources.redhat.com>,
Richard.Earnshaw@arm.com
Subject: Re: gdb 5.3 problem in ARM simulator
Date: Fri, 25 Apr 2003 21:21:00 -0000 [thread overview]
Message-ID: <200304251457.h3PEvIA02068@pc960.cambridge.arm.com> (raw)
In-Reply-To: Your message of "Fri, 25 Apr 2003 16:40:06 +0200." <84B8B0CA0E7AC24C8EEB89B90BF8888F0190BC65@fthw9fka.os.fth.sbs.de>
I suspect that all of these problems stem from the fact that GDB is using
the wrong method for resetting the PC. Instead of setting state->Reg[15]
directly or using ARMul_SetReg() it should be using ARMul_SetR15() as the
RDI interface does. Then both your and Nick's previous change shouldn't
be needed.
However, I haven't tested any of this, it's just an observation I made
when looking over the source code one day.
R.
prev parent reply other threads:[~2003-04-25 14:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-25 16:53 Hornung Peter
2003-04-25 21:21 ` Richard Earnshaw [this message]
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=200304251457.h3PEvIA02068@pc960.cambridge.arm.com \
--to=rearnsha@arm.com \
--cc=Richard.Earnshaw@arm.com \
--cc=gdb-patches@sources.redhat.com \
--cc=peter_hornung@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