From: "Maciej W. Rozycki" <macro@mips.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sourceware.org, Nigel Stephens <nigel@mips.com>,
"Maciej W. Rozycki" <macro@linux-mips.org>
Subject: Re: Disassemble branch delay slot instructions automatically
Date: Fri, 18 May 2007 15:47:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.61.0705181625420.28428@perivale.mips.com> (raw)
In-Reply-To: <20070516153242.GA8062@caradoc.them.org>
On Wed, 16 May 2007, Daniel Jacobowitz wrote:
> I would like additional opinions on this patch.
I wouldn't mind either.
> My first reaction was "hey, that would be useful to me", but my second
> was concern that this would upset a GDB/MI frontend. We should at
> least try to provoke a problem in one such frontend first.
Well, do_examine() is used by the "display" and "x" commands only which
are not used by any other frontend it would seem. Of course you can issue
these commands from MI (or from the Insight console window), but that
should not be an issue as these are not commands meant to be used by
programs interfacing to this frontend (that would be "-data-disassemble"
which uses some other code).
I have a follow-on patch that makes the output of "display /i" look
better, which I will submit straight away.
Maciej
next prev parent reply other threads:[~2007-05-18 15:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-15 18:13 Maciej W. Rozycki
2007-05-16 15:32 ` Daniel Jacobowitz
2007-05-18 15:47 ` Maciej W. Rozycki [this message]
2007-06-13 16:56 ` Daniel Jacobowitz
2007-06-20 13:56 ` Maciej W. Rozycki
2007-06-20 14:09 ` Daniel Jacobowitz
2007-06-20 15:25 ` Maciej W. Rozycki
2007-06-20 18:37 ` Eli Zaretskii
2007-06-21 15:19 ` Maciej W. Rozycki
2007-06-21 19:01 ` Eli Zaretskii
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=Pine.LNX.4.61.0705181625420.28428@perivale.mips.com \
--to=macro@mips.com \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=macro@linux-mips.org \
--cc=nigel@mips.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