From: Pedro Alves <palves@redhat.com>
To: Paul_Koning@Dell.com, jhb@freebsd.org
Cc: gdb-patches@sourceware.org, k.toshihito@yahoo.de
Subject: Re: [PATCH] Add a new format letter to dump instructions backward
Date: Mon, 25 Jan 2016 18:27:00 -0000 [thread overview]
Message-ID: <56A6691A.3060400@redhat.com> (raw)
In-Reply-To: <3F40FBEE-2395-4ECC-94A0-A395B35B788C@dell.com>
On 01/25/2016 06:22 PM, Paul_Koning@Dell.com wrote:
>
>> On Jan 25, 2016, at 12:52 PM, John Baldwin <jhb@freebsd.org> wrote:
>>
>> On Monday, January 25, 2016 11:41:27 AM Pedro Alves wrote:
>>> On 01/24/2016 09:28 PM, Toshihito Kikuchi wrote:
>>> ...
>>> #3 - negative repeat counts ?
>>>
>>> (gdb) x /4i // next 4 instructions
>>> (gdb) x /-4i // previous 4 instructions
>>> ...
>>> #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.
>
> Yes, but how do you do instructions backwards if the instruction length is variable? It is entirely possible that there will be multiple possible answers, and no way to tell which one (if any) is "correct".
You disassemble forward starting from the previous known
instruction boundary, based on symbol/line info. I haven't looked
at the implementation in detail, but from the patch description, that's
what I assume the patch is doing.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2016-01-25 18:27 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
2016-01-25 18:22 ` Paul_Koning
2016-01-25 18:27 ` Pedro Alves [this message]
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=56A6691A.3060400@redhat.com \
--to=palves@redhat.com \
--cc=Paul_Koning@Dell.com \
--cc=gdb-patches@sourceware.org \
--cc=jhb@freebsd.org \
--cc=k.toshihito@yahoo.de \
/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