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

On Wednesday 04 March 2009 22:14:32, Eli Zaretskii wrote:
> > Date: Wed, 4 Mar 2009 13:25:05 -0800
> > From: Doug Evans <dje@google.com>
> > Cc: gdb@sourceware.org, Daniel Jacobowitz <drow@false.org>,         Eli Zaretskii <eliz@gnu.org>, teawater@gmail.com
> > 
> > Ya, extending the disassemble command makes sense to me.
> 
> I don't see how it can make sense that the same command does both
> one-time disassembly and disassemble the next source line each time
> GDB stops.  It's like "print" and "display" -- it's not an accident we
> have 2 different commands there.

Certainly.  I was just pointing out that the "disassembly"
command could have said option.  I had a hook-stop in mind --- if it
had such an option already, the user could could just set a hook-stop
to show the disassembly of the current source line.

> If anything, extending "display" with yet another format specifier, or
> maybe a qualifier for /i, would make much more sense to me.

Of course, I don't disagree.  Daniel surely mentioned "x/i", because
"display" takes the exact same formats as the "x" command does.

-- 
Pedro Alves


  reply	other threads:[~2009-03-04 22:20 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
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 [this message]
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=200903042220.38093.pedro@codesourcery.com \
    --to=pedro@codesourcery.com \
    --cc=dje@google.com \
    --cc=drow@false.org \
    --cc=eliz@gnu.org \
    --cc=gdb@sourceware.org \
    --cc=teawater@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