Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Peng Yu via Gdb <gdb@sourceware.org>
To: Christo Crause <christo.crause@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: How to display instructions around the current instuction?
Date: Thu, 28 Jan 2021 11:45:10 -0600	[thread overview]
Message-ID: <CABrM6wnOA15=Ost+ScWxc53V6215jo7RX7SdprR+tnMZRKHn0w@mail.gmail.com> (raw)
In-Reply-To: <CAGOmfbFh+6AJZFsDP8nFH1bs6kntC4khO+YmPkn3LUfcLAspZw@mail.gmail.com>

Hi Christo,

> Another possibility could be: set disassemble-next-line on

This does not correctly answer the question. It just show the current
line but not the context.

Also, how to just show the disassembled code but the hex numbers.

I know the doc is here. But is there is a way to check its helpage
withing gdb command line? Thanks.

https://visualgdb.com/gdbreference/commands/set_disassemble-next-line

Temporary breakpoint 1, 0x0000000000401134 in main ()
=> 0x0000000000401134 <main+4>:	48 83 ec 10	sub    rsp,0x10
(gdb) 0x0000000000401138 in main ()
=> 0x0000000000401138 <main+8>:	c7 45 fc 00 00 00 00	mov    DWORD PTR
[rbp-0x4],0x0
(gdb) 0x000000000040113f in main ()
=> 0x000000000040113f <main+15>:	48 bf 04 20 40 00 00 00 00 00	movabs
rdi,0x402004

-- 
Regards,
Peng

  parent reply	other threads:[~2021-01-28 17:45 UTC|newest]

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

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='CABrM6wnOA15=Ost+ScWxc53V6215jo7RX7SdprR+tnMZRKHn0w@mail.gmail.com' \
    --to=gdb@sourceware.org \
    --cc=christo.crause@gmail.com \
    --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