From: Michael Snyder <msnyder@specifix.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Doug Evans <dje@google.com>, gdb-patches@sourceware.org
Subject: Re: [RFA] mixed source+assembly from cli disassemble
Date: Fri, 11 Apr 2008 08:55:00 -0000 [thread overview]
Message-ID: <1207869204.31772.416.camel@localhost.localdomain> (raw)
In-Reply-To: <20080410081549.GA3589@adacore.com>
On Thu, 2008-04-10 at 01:15 -0700, Joel Brobecker wrote:
> > Going on a week...
> > No other comments, pro or con?
>
> I really like the idea, it's something that I often wished we'd have
> (and often asked for in graphical front-ends). I was going to review
> the patch, but wanted to ask others to comment on the user interface
> first. Once we agree on the syntax, then I can review the patch itself.
>
> Doug suggests to use an optional "/s" modifier. For instance:
>
> (gdb) disassemble ADDR -> regular assembly listing
> (gdb) disassemble /s ADDR -> intermixed source+assembly listing
>
> Is that OK with everyone? It's pretty consistent with what we do
> for the print command, so I like it.
I think using a '/' modifier is good, since that's what
we use for print and examine and so on.
The choice of the letter 's' is probably as good as any.
The only other one that comes to my mind is 'm' (for "mixed").
And I'm not expressing a preference or objection.
next prev parent reply other threads:[~2008-04-10 23:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-04 3:26 Doug Evans
2008-04-04 9:17 ` Michael Snyder
2008-04-04 9:26 ` Doug Evans
2008-04-04 9:58 ` Eli Zaretskii
2008-04-09 22:27 ` Michael Snyder
2008-04-10 12:35 ` Joel Brobecker
2008-04-11 8:55 ` Michael Snyder [this message]
2008-04-15 20:32 ` Michael Snyder
2008-04-16 21:16 ` Joel Brobecker
2008-04-16 21:22 ` Doug Evans
2008-04-16 22:49 ` Doug Evans
2008-04-17 21:29 ` Joel Brobecker
2008-04-17 22:01 ` Daniel Jacobowitz
2008-04-17 22:45 ` Joel Brobecker
2008-04-28 18:52 ` Fwd: " Doug Evans
2008-04-29 0:54 ` Eli Zaretskii
2008-05-06 3:15 ` Doug Evans
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=1207869204.31772.416.camel@localhost.localdomain \
--to=msnyder@specifix.com \
--cc=brobecker@adacore.com \
--cc=dje@google.com \
--cc=gdb-patches@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