From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org, Eli Zaretskii <eliz@gnu.org>
Cc: Daniel Jacobowitz <drow@false.org>,
teawater@gmail.com, brobecker@adacore.com, msnyder@vmware.com
Subject: Re: [RFA] Displaced stepping just enable in non-stop mode
Date: Fri, 17 Oct 2008 14:51:00 -0000 [thread overview]
Message-ID: <200810171550.41055.pedro@codesourcery.com> (raw)
In-Reply-To: <uzll4mm7q.fsf@gnu.org>
On Thursday 16 October 2008 19:25:13, Eli Zaretskii wrote:
> Since we are prepared to decide that turning non-stop turns on
> displaced stepping, I understand that in most cases displaced stepping
> does work, which brings me to the conclusion that we could use
> displaced stepping even without non-stop.
The target itself could support stepping over breakpoints
without requiring us to use displaced stepping on the core
side. DICOS falls in that category, I just haven't submitted
the patch yet to make the target report support for it (along with a
qSupported feature). If the target doesn't report support for it, we
fallback to displaced stepping, and that requires gdbarch support.
> We could also try to detect if it works, and display a warning if we
> think it won't (RE the cases you described above).
That would be a warning that brings no value to the user in
all-stop mode.
If the user sees:
"warning: you can not use displaced stepping on this platform".
He/she will think that something is wrong, while at least currently,
no functionality the user cares for is lost (in all-stop).
> > I'm not sure what else to call displaced stepping. "Step around
> > breakpoints"?
>
> The text mentions "out-of-line stepping", which sounds better to me.
I have no idea why "displaced stepping" was chosen in the first
place --- that pre-dates me.
--
Pedro Alves
next prev parent reply other threads:[~2008-10-17 14:51 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
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 [this message]
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=200810171550.41055.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=brobecker@adacore.com \
--cc=drow@false.org \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=msnyder@vmware.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