Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <dan@codesourcery.com>
To: Matthew Gretton-Dann <matthew.gretton-dann@arm.com>
Cc: 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 13:40:00 -0000	[thread overview]
Message-ID: <20100304133944.GA21490@caradoc.them.org> (raw)
In-Reply-To: <1267703327.13980.13.camel@e102111-lin.cambridge.arm.com>

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.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2010-03-04 13:40 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 [this message]
2010-03-04 14:09   ` Eli Zaretskii
2010-03-04 17:38   ` Doug Evans

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=20100304133944.GA21490@caradoc.them.org \
    --to=dan@codesourcery.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