From: Doug Evans <dje@google.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb@sourceware.org, Daniel Jacobowitz <drow@false.org>,
Eli Zaretskii <eliz@gnu.org>,
teawater@gmail.com
Subject: Re: What about add a interface to output the assembly codes follow inferior execution
Date: Wed, 04 Mar 2009 21:25:00 -0000 [thread overview]
Message-ID: <e394668d0903041325m516dca91tb8f3ff7ce4bec3a6@mail.gmail.com> (raw)
In-Reply-To: <200903041932.04620.pedro@codesourcery.com>
On Wed, Mar 4, 2009 at 11:32 AM, Pedro Alves <pedro@codesourcery.com> wrote:
> On Wednesday 04 March 2009 19:26:47, Daniel Jacobowitz wrote:
>> (Another thing that would be useful, perhaps, is a modifier to 'x/i' to
>> say "a line's worth of instructions". But I think we'd have a lot of
>> trouble finding a non-ambiguous command for that.)
>>
>
> I was thinking the same, while noticing that the
> "disassemble" command also doesn't allow a line number or line
> number range.
>
> Did I mention already that with the TUI one can see disassembly
> and source code at the same time easily ? :-)
Ya, extending the disassemble command makes sense to me.
next prev parent reply other threads:[~2009-03-04 21:25 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 [this message]
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=e394668d0903041325m516dca91tb8f3ff7ce4bec3a6@mail.gmail.com \
--to=dje@google.com \
--cc=drow@false.org \
--cc=eliz@gnu.org \
--cc=gdb@sourceware.org \
--cc=pedro@codesourcery.com \
--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