public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@palves.net>
To: gdb@sourceware.org
Subject: Re: How to display instructions around the current instuction?
Date: Thu, 28 Jan 2021 18:27:03 +0000	[thread overview]
Message-ID: <8ff04714-9feb-d13a-98e3-cede442e0eb8@palves.net> (raw)
In-Reply-To: <CABrM6wnFF3Gz9B62qeoqGgRZo0D-djpKPh-X6LmXGYEapqBYQw@mail.gmail.com>


On 27/01/21 23:12, Peng Yu via Gdb wrote:
> Hi,
> 
> The following command will disply instructions below the current
> instructions. Is there a way to display around the current instruction
> (e.g., 5 instructions above and 5 instructions below)?
> 
> 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*)>
~~~~

There's also this:

~~~~
(gdb) help set disassemble-next-line 
Set whether to disassemble next source line or insn when execution stops.
If ON, GDB will display disassembly of the next source line, in addition
to displaying the source line itself.  If the next source line cannot
be displayed (e.g., source is unavailable or there's no line info), GDB
will display disassembly of next instruction instead of showing the
source line.
If AUTO, display disassembly of next instruction only if the source line
cannot be displayed.
If OFF (which is the default), never display the disassembly of the next
source line.
(gdb) 
~~~~

  parent reply	other threads:[~2021-01-28 18:27 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 [this message]
2021-01-29  1:58   ` Peng Yu
2021-01-29  7:18     ` 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=8ff04714-9feb-d13a-98e3-cede442e0eb8@palves.net \
    --to=pedro@palves.net \
    --cc=gdb@sourceware.org \
    /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).