From: teawater <teawater@gmail.com>
To: "Eli Zaretskii" <eliz@gnu.org>
Cc: msnyder@vmware.com, pedro@codesourcery.com,
gdb-patches@sourceware.org, brobecker@adacore.com
Subject: Re: [RFA] Displaced stepping just enable in non-stop mode
Date: Fri, 17 Oct 2008 16:09:00 -0000 [thread overview]
Message-ID: <daef60380810170908k5eabcfe7k8e77e05111abc81c@mail.gmail.com> (raw)
In-Reply-To: <uk5c7mtg7.fsf@gnu.org>
I think "set displace-break-insn" is not right.
It will make user think breakpoint insn move to another address.
Actually this function try to don't move breakpoint insn in step.
On Fri, Oct 17, 2008 at 18:01, Eli Zaretskii <eliz@gnu.org> wrote:
>> Date: Fri, 17 Oct 2008 13:45:36 +0800
>> From: teawater <teawater@gmail.com>
>> Cc: "Eli Zaretskii" <eliz@gnu.org>, pedro@codesourcery.com,
>> gdb-patches@sourceware.org, brobecker@adacore.com
>>
>> How about "set step displace"
>>
>> I think "displace" is clear.
>
> It isn't clear to me. "Displace" means simply "move forcefully".
> What is actually being moved here is the breakpoint instruction, but
> "set step displace" includes no hints for that.
>
> Maybe "set displace-break-insn" or some such.
>
next prev parent reply other threads:[~2008-10-17 16:09 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 [this message]
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=daef60380810170908k5eabcfe7k8e77e05111abc81c@mail.gmail.com \
--to=teawater@gmail.com \
--cc=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=msnyder@vmware.com \
--cc=pedro@codesourcery.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