From: Andreas Schwab <schwab@linux-m68k.org>
To: Peng Yu <pengyu.ut@gmail.com>
Cc: Peng Yu via Gdb <gdb@sourceware.org>
Subject: Re: How to display instructions around the current instuction?
Date: Thu, 28 Jan 2021 19:44:03 +0100 [thread overview]
Message-ID: <87o8h86gwc.fsf@igel.home> (raw)
In-Reply-To: <CABrM6wnvTx0XtiFttpj+OQiY6rk+eDsiXs0xaD_75ivMM2XVig@mail.gmail.com> (Peng Yu's message of "Thu, 28 Jan 2021 11:08:57 -0600")
On Jan 28 2021, Peng Yu wrote:
> There could be a syntax to go back a given number of instructions.
How do you know how long each instruction is?
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next prev parent reply other threads:[~2021-01-28 18:44 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 [this message]
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
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=87o8h86gwc.fsf@igel.home \
--to=schwab@linux-m68k.org \
--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