From: John Baldwin <jhb@freebsd.org>
To: gdb-patches@sourceware.org
Cc: Pedro Alves <palves@redhat.com>,
Toshihito Kikuchi <k.toshihito@yahoo.de>
Subject: Re: [PATCH] Add a new format letter to dump instructions backward
Date: Mon, 25 Jan 2016 18:10:00 -0000 [thread overview]
Message-ID: <2015581.ugHgmqoO9R@ralph.baldwin.cx> (raw)
In-Reply-To: <56A609E7.6050903@redhat.com>
On Monday, January 25, 2016 11:41:27 AM Pedro Alves wrote:
> On 01/24/2016 09:28 PM, Toshihito Kikuchi wrote:
> Seems to me that some other UI would be better. E.g.,:
>
> #1 - a different switch, like "x -back /i " ?
>
> #2 - a different command, like "bx" ?
>
> #3 - negative repeat counts ?
>
> (gdb) x /4i // next 4 instructions
> (gdb) x /-4i // previous 4 instructions
>
> (gdb) x /4bx // next 4 bytes, in hex
> (gdb) x /-4bx // previous 4 bytes, in hex
>
>
> Added #1 just for completeness, I don't find it very convenient.
>
> #3 feels natural to me. What do you (and others) think?
I think #3 is the most natural as well. I also think this is a
very useful feature.
--
John Baldwin
next prev parent reply other threads:[~2016-01-25 18:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1827952218.466587.1453670934999.JavaMail.yahoo.ref@mail.yahoo.com>
2016-01-24 21:31 ` Toshihito Kikuchi
2016-01-25 11:41 ` Pedro Alves
2016-01-25 18:10 ` John Baldwin [this message]
2016-01-25 18:22 ` Paul_Koning
2016-01-25 18:27 ` Pedro Alves
2016-01-25 20:11 ` Paul_Koning
2016-01-26 5:39 ` Toshihito Kikuchi
2016-01-27 16:04 ` Andrew Burgess
2016-01-27 20:09 ` Paul_Koning
2016-01-28 11:53 ` Pedro Alves
2016-02-07 23:19 ` [PATCH] Negative repeat count for 'x' command Toshihito Kikuchi
2016-02-17 11:38 ` Pedro Alves
2016-03-23 0:27 ` Toshihito Kikuchi
2016-04-11 12:17 ` Pedro Alves
2016-04-15 0:30 ` Toshihito Kikuchi
[not found] ` <5714DE73.5010104@redhat.com>
2016-04-28 18:06 ` Toshihito Kikuchi
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=2015581.ugHgmqoO9R@ralph.baldwin.cx \
--to=jhb@freebsd.org \
--cc=gdb-patches@sourceware.org \
--cc=k.toshihito@yahoo.de \
--cc=palves@redhat.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