From: Doug Evans <dje@google.com>
To: Matthew Gretton-Dann <matthew.gretton-dann@arm.com>,
gdb-patches@sourceware.org
Subject: Re: [PATCH] [ARM] Improve heuristic to guess the instruction state for the next PC when single-stepping
Date: Thu, 04 Mar 2010 17:38:00 -0000 [thread overview]
Message-ID: <e394668d1003040937l3aaa09a6v267f047b4d38c564@mail.gmail.com> (raw)
In-Reply-To: <20100304133944.GA21490@caradoc.them.org>
On Thu, Mar 4, 2010 at 5:39 AM, Daniel Jacobowitz <dan@codesourcery.com> wrote:
> On Thu, Mar 04, 2010 at 11:48:47AM +0000, Matthew Gretton-Dann wrote:
>> This patch attempts to fix this by seeing if arm_pc_is_thumb () is being
>> asked about the address we will end up at if we execute the instruction
>> at the current PC. If so it 'executes' the current instruction to see
>> if it will change state, and uses this information to determine the
>> return value.
>
> This is a cute approach. I can't think of any potential problems with
> it, so I'll commit your patch.
>
>> 2010-03-04 Matthew Gretton-Dann <matthew.gretton-dann@arm.com>
>>
>> * arm-tdep.c (arm_pc_is_thumb): Add heuristic that tries to get
>> the state right when single stepping.
>> (arm_get_next_pc_raw, thumb_get_next_pc_raw): New functions.
>> Get the next PC along with the instruction state.
>> (thumb_get_next_pc): Remove.
>> (arm_get_next_pc): Modified to use arm_get_next_pc_raw ().
>
> At some point we were asked to not use " ()" to indicate functions, so
> I've removed that bit.
Would it be nice to prefer what the hardware says over what the symbol
info says?
[And if the symbol info disagrees flag a warning?]
[The heuristic is done after symbol checks.]
prev parent reply other threads:[~2010-03-04 17:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-04 11:48 Matthew Gretton-Dann
2010-03-04 13:40 ` Daniel Jacobowitz
2010-03-04 14:09 ` Eli Zaretskii
2010-03-04 17:38 ` Doug Evans [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=e394668d1003040937l3aaa09a6v267f047b4d38c564@mail.gmail.com \
--to=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=matthew.gretton-dann@arm.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