Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: teawater <teawater@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: dje@google.com, drow@false.org, gdb@sourceware.org
Subject: Re: What about add a interface to output the assembly codes follow  	inferior execution
Date: Wed, 04 Mar 2009 05:30:00 -0000	[thread overview]
Message-ID: <daef60380903032130n3e249eeapc3c3635e94bd6090@mail.gmail.com> (raw)
In-Reply-To: <u3adund5j.fsf@gnu.org>

Thanks Eli.

I think "show-opcodes" is very good.  :)

Hui

On Wed, Mar 4, 2009 at 12:08, Eli Zaretskii <eliz@gnu.org> wrote:
>> Date: Wed, 4 Mar 2009 10:28:48 +0800
>> From: teawater <teawater@gmail.com>
>> Cc: gdb ml <gdb@sourceware.org>
>>
>> When exec-disassemble is on,
>> If the $pc doesn't have the line message, gdb will output the assembly
>> code for $pc.
>> If the $pc has the line message, gdb will output the assembly codes of
>> this line.
>
> I think this is a useful feature, but we need a better name for it.
> Something like show-opcodes, for example.
>


  reply	other threads:[~2009-03-04  5:30 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-03  3:11 teawater
2009-03-03 16:42 ` Doug Evans
2009-03-03 17:04   ` Daniel Jacobowitz
2009-03-04  2:29     ` teawater
2009-03-04  4:09       ` Eli Zaretskii
2009-03-04  5:30         ` teawater [this message]
2009-03-04 17:15           ` Doug Evans
2009-03-04 19:09             ` Eli Zaretskii
2009-03-04 19:20               ` Pedro Alves
2009-03-04 22:10                 ` Eli Zaretskii
2009-03-04 19:24               ` Doug Evans
2009-03-04 19:26               ` Daniel Jacobowitz
2009-03-04 19:32                 ` Pedro Alves
2009-03-04 21:25                   ` Doug Evans
2009-03-04 22:14                     ` Eli Zaretskii
2009-03-04 22:20                       ` Pedro Alves
2009-03-04 22:31                       ` Doug Evans
2009-03-04 23:41                 ` Tom Tromey
2009-03-05  2:42                   ` teawater

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=daef60380903032130n3e249eeapc3c3635e94bd6090@mail.gmail.com \
    --to=teawater@gmail.com \
    --cc=dje@google.com \
    --cc=drow@false.org \
    --cc=eliz@gnu.org \
    --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