From: Samuel Bronson <naesten@gmail.com>
To: gdb-patches@sourceware.org
Subject: Re: Support for single-stepping Thumb-2 programs
Date: Wed, 29 Jul 2009 01:14:00 -0000 [thread overview]
Message-ID: <87tz0wqwpq.wl%naesten@gmail.com> (raw)
In-Reply-To: <20090728163645.GA22855@caradoc.them.org>
At Tue, 28 Jul 2009 12:36:45 -0400,
Daniel Jacobowitz wrote:
> So the patch does not allow single stepping inside an IT block. Not
> explicitly mentioned in the patch is that it also doesn't address
> setting breakpoints inside an IT block, which has the same problem.
>
> My best plan to date to handle stepping is to reuse displaced stepping
> for this somehow. Fill the rest of the IT block with breakpoints or
> nops to simulate just the instruction we're interested in. As for
> user set breakpoints, I think we'll have to adjust them to point at
> the IT instruction instead.
>
> I haven't implemented any of that yet. This is generally useful
> as-is, so I'm submitting it without those potential improvements.
So ... shouldn't this be documented in the manual until you do
implement that single-stepping?
next prev parent reply other threads:[~2009-07-28 22:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-28 17:34 Daniel Jacobowitz
2009-07-29 1:14 ` Samuel Bronson [this message]
2009-07-29 18:46 ` Daniel Jacobowitz
2009-10-13 22:48 ` Daniel Jacobowitz
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=87tz0wqwpq.wl%naesten@gmail.com \
--to=naesten@gmail.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