From: Daniel Jacobowitz <drow@false.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Pedro Alves <pedro@codesourcery.com>,
teawater@gmail.com, gdb-patches@sourceware.org,
brobecker@adacore.com, msnyder@vmware.com
Subject: Re: [RFA] Displaced stepping just enable in non-stop mode
Date: Thu, 16 Oct 2008 12:35:00 -0000 [thread overview]
Message-ID: <20081016123422.GA31057@caradoc.them.org> (raw)
In-Reply-To: <u8wspnekq.fsf@gnu.org>
On Thu, Oct 16, 2008 at 10:12:37AM +0200, Eli Zaretskii wrote:
> . Why isn't it better to use displaced stepping, if supported, even
> if non-stop mode is not in effect? I think the linkage between
> the two is confusing and unnecessary.
It is generally good to use displaced stepping. But in some
circumstances it is slower, and in others it doesn't work at all. It
requires we have a small scratchpad area on the target which is
writeable and executable. By default we use the area at _start; this
doesn't work on some simulator targets, on targets which execute code
from ROM or flash memory, or during reverse debugging.
Some of those cases could be fixed by adding a user knob for where to
put the scratchpad, though others can't.
It's linked to non-stop because for non-stop it is required.
I'm not sure what else to call displaced stepping. "Step around
breakpoints"?
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-10-16 12:35 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-07 6:27 teawater
2008-10-07 12:18 ` Joel Brobecker
2008-10-08 6:11 ` teawater
2008-10-09 14:50 ` Pedro Alves
2008-10-10 3:38 ` teawater
2008-10-14 7:36 ` teawater
2008-10-16 0:07 ` Pedro Alves
2008-10-16 2:29 ` teawater
2008-10-16 2:39 ` Daniel Jacobowitz
2008-10-16 2:59 ` Pedro Alves
2008-10-22 3:16 ` teawater
2008-10-22 19:48 ` Eli Zaretskii
2008-10-23 8:13 ` teawater
2008-10-23 12:57 ` Pedro Alves
2008-10-24 2:49 ` teawater
2008-10-16 8:13 ` Eli Zaretskii
2008-10-16 12:35 ` Daniel Jacobowitz [this message]
2008-10-16 18:27 ` Eli Zaretskii
2008-10-16 18:33 ` Daniel Jacobowitz
2008-10-16 21:19 ` Michael Snyder
2008-10-17 5:46 ` teawater
2008-10-17 10:02 ` Eli Zaretskii
2008-10-17 15:05 ` Pedro Alves
2008-10-17 16:09 ` teawater
2008-10-17 14:48 ` Pedro Alves
2008-10-17 16:01 ` teawater
2008-10-17 17:33 ` Michael Snyder
2008-10-17 19:47 ` Jakob Engblom
2008-10-17 19:49 ` Michael Snyder
2008-10-17 14:51 ` Pedro Alves
2008-10-17 15:53 ` Eli Zaretskii
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=20081016123422.GA31057@caradoc.them.org \
--to=drow@false.org \
--cc=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=msnyder@vmware.com \
--cc=pedro@codesourcery.com \
--cc=teawater@gmail.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