From: Yao Qi <yao@codesourcery.com>
To: gdb-patches@sourceware.org
Subject: [PING : rfa] Update PC without side effect in displaced stepping
Date: Thu, 06 Jan 2011 14:19:00 -0000 [thread overview]
Message-ID: <4D25CF4D.8070008@codesourcery.com> (raw)
In-Reply-To: <4D12F3A8.3020102@codesourcery.com>
On 12/23/2010 03:00 PM, Yao Qi wrote:
> OK. I have to try the second approach, which is 1) exposing displaced
> stepping state to tdep, and 2) take displaced stepping state into
> account when determining the mode.
Ping.
http://sourceware.org/ml/gdb-patches/2010-12/msg00427.html
2010-12-23 Yao Qi <yao@codesourcery.com>
* arm-tdep.c: (arm_pc_is_thumb): Adjust MEMADDR if it is within
copy area of displaced stepping.
* infrun.c (struct displaced_step_inferior_state): Move to ...
Expose get_displaced_stepping_state.
* inferior.h: ... here.
Declare get_displaced_stepping_state.
P.S. I am thinking that it may be a good idea to move code for
displaced stepping to a separate file, say displaced_step.[ch]. Comments?
--
Yao (é½å°§)
next prev parent reply other threads:[~2011-01-06 14:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-20 7:50 [rfa] " Yao Qi
2010-12-20 8:06 ` Mark Kettenis
2010-12-20 13:42 ` Yao Qi
2010-12-21 16:19 ` Yao Qi
2010-12-23 4:54 ` Joel Brobecker
2010-12-23 8:45 ` Yao Qi
2011-01-06 14:19 ` Yao Qi [this message]
2011-01-12 5:39 ` [try 3rd] arm_pc_is_thumb takes displaced stepping into account Yao Qi
2011-01-13 15:55 ` Matthew Gretton-Dann
2011-01-13 16:34 ` Yao Qi
2011-01-19 16:09 ` [Ping 1: try " Yao Qi
2011-01-30 3:21 ` [Ping 2: " Yao Qi
2011-01-31 15:40 ` [try " Ulrich Weigand
2011-02-10 6:42 ` Yao Qi
2011-02-15 21:15 ` Ulrich Weigand
2010-12-23 12:04 ` [rfa] Update PC without side effect in displaced stepping Mark Kettenis
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=4D25CF4D.8070008@codesourcery.com \
--to=yao@codesourcery.com \
--cc=gdb-patches@sourceware.org \
/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