public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Peng Yu <pengyu.ut@gmail.com>
Cc: pedro@palves.net, gdb@sourceware.org
Subject: Re: How to display instructions around the current instuction?
Date: Fri, 29 Jan 2021 09:18:35 +0200	[thread overview]
Message-ID: <83tur0xlbo.fsf@gnu.org> (raw)
In-Reply-To: <CABrM6w=40RLHFwoxMquB-iF=c5S3qxa43H9_vrnyq41tjgj_HQ@mail.gmail.com> (message from Peng Yu via Gdb on Thu, 28 Jan 2021 19:58:11 -0600)

> Date: Thu, 28 Jan 2021 19:58:11 -0600
> From: Peng Yu via Gdb <gdb@sourceware.org>
> Cc: gdb@sourceware.org
> 
> >> display/10i $rip
> >>
> >
> > From gdb/NEWS:
> >
> > ~~~~
> > *** Changes in GDB 7.12
> >
> > * GDB now supports a negative repeat count in the 'x' command to examine
> >   memory backward from the given address.  For example:
> >
> > ...
> >     (gdb) x/-5i 0x0000000000400580
> >        0x40056a <main(int, char**)+8>:      mov    %edi,-0x4(%rbp)
> >        0x40056d <main(int, char**)+11>:     mov    %rsi,-0x10(%rbp)
> >        0x400571 <main(int, char**)+15>:     mov    $0x40061c,%esi
> >        0x400576 <main(int, char**)+20>:     mov    $0x2a,%edi
> >        0x40057b <main(int, char**)+25>:
> >         callq  0x400536 <Func1(int, char const*)>
> > ~~~~
> 
> Is there a documentation problem in gdb regarding this feature. I
> don't see this feature is documented.

You are looking up help on a wrong command.  Pedro suggested to use

   x/-5i ADDRESS

And the help for 'x' says:

  The specified number of objects of the specified size are printed
  according to the format.  If a negative number is specified, memory is
  examined backward from the address.

Note the last sentence.

      reply	other threads:[~2021-01-29  7:18 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-27 23:12 Peng Yu
2021-01-28  8:48 ` Andreas Schwab
2021-01-28 17:08   ` Peng Yu
2021-01-28 18:44     ` Andreas Schwab
2021-01-29 17:38       ` Tavis Ormandy
2021-01-28  9:19 ` Stefan Puiu
2021-01-28 17:06   ` Peng Yu
2021-01-28 17:26     ` Eli Zaretskii
2021-01-28 17:37       ` Peng Yu
2021-01-28 17:41         ` Christian Biesinger
2021-01-29  2:07           ` Peng Yu
2021-01-29  2:22             ` Sterling Augustine
2021-01-29  2:32               ` Peng Yu
2021-01-29  2:47                 ` Sterling Augustine
2021-01-28 17:57         ` Eli Zaretskii
2021-01-28 18:00     ` Stefan Puiu
2021-01-29  2:15       ` Peng Yu
2021-01-28 13:11 ` Christian Biesinger
2021-01-28 16:50   ` Peng Yu
2021-01-28 16:53     ` Christian Biesinger
2021-01-28 17:16       ` Peng Yu
2021-01-28 17:16         ` Christian Biesinger
2021-01-28 17:00     ` Sterling Augustine
     [not found]       ` <CAGOmfbFh+6AJZFsDP8nFH1bs6kntC4khO+YmPkn3LUfcLAspZw@mail.gmail.com>
2021-01-28 17:45         ` Peng Yu
2021-01-28 18:27 ` Pedro Alves
2021-01-29  1:58   ` Peng Yu
2021-01-29  7:18     ` Eli Zaretskii [this message]

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=83tur0xlbo.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb@sourceware.org \
    --cc=pedro@palves.net \
    --cc=pengyu.ut@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).