From: Stefan Puiu <stefan.puiu@gmail.com>
To: Peng Yu <pengyu.ut@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: How to display instructions around the current instuction?
Date: Thu, 28 Jan 2021 11:19:37 +0200 [thread overview]
Message-ID: <CACKs7VAc7tYS-NR8yDnCjDr0z39_-M=QDqbS7O0Lzz-eLk9Rng@mail.gmail.com> (raw)
In-Reply-To: <CABrM6wnFF3Gz9B62qeoqGgRZo0D-djpKPh-X6LmXGYEapqBYQw@mail.gmail.com>
Hi,
On Thu, Jan 28, 2021 at 1:31 AM Peng Yu via Gdb <gdb@sourceware.org> 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
Have you tried something using '$rip-10' in your command?
display/10i $rip-10
I don't think x86-64 instructions have fixed width, so that won't
always print the same number of instructions before the current one,
but it's probably a good approximation.
next prev parent reply other threads:[~2021-01-28 9:19 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 [this message]
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
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='CACKs7VAc7tYS-NR8yDnCjDr0z39_-M=QDqbS7O0Lzz-eLk9Rng@mail.gmail.com' \
--to=stefan.puiu@gmail.com \
--cc=gdb@sourceware.org \
--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).