From: Daniel Jacobowitz <drow@false.org>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: Maxim Grigoriev <maxim@tensilica.com>,
gdb-patches@sources.redhat.com,
Pete MacLiesh <pmac@tensilica.com>,
Marc Gauthier <marc@tensilica.com>,
Ross Morley <ross@tensilica.com>
Subject: Re: [PATCH] MI and MI2 should have identical behavior on -target-download command
Date: Tue, 21 Aug 2007 13:28:00 -0000 [thread overview]
Message-ID: <20070821132753.GA25612@caradoc.them.org> (raw)
In-Reply-To: <18122.55169.70021.143467@kahikatea.snap.net.nz>
On Wed, Aug 22, 2007 at 12:16:01AM +1200, Nick Roberts wrote:
> > It fixes a small glitch in GDB MI. MI2 is a default. So
> > MI and MI2 should work identically. The MI2 being set as
> > a default is hard-coded in several places. I think one
> > place was missed:
> >
> > mi/mi-main.c::mi_load_progress().
Sorry, we (specifically Andrew Stubbs) noticed this problem in
November 2005, but no one got around to fixing it.
> > Without this fix, MI "-target-download" command behaves
> > differently on MI versus MI2 not showing loading progress,
> > when "-i=mi2" is used.
> >
> > GDB front-ends developers might want to stick with "-i=mi"
> > assuming they always use a default. It would be a bad idea
> > to force them to use explicit options like "-i=mi2".
>
> What behaviour do you want for mi3?
MI3 should probably print the progress indicator too. Like below.
Anyone disagree with this patch?
--
Daniel Jacobowitz
CodeSourcery
2007-08-21 Maxim Grigoriev <maxim2405@gmail.com>
Daniel Jacobowitz <dan@codesourcery.com>
* mi-main.c (mi_load_progress): Handle MI2 and MI3 interpreters.
Index: mi-main.c
===================================================================
RCS file: /cvs/src/src/gdb/mi/mi-main.c,v
retrieving revision 1.101
diff -u -p -r1.101 mi-main.c
--- mi-main.c 10 Aug 2007 21:52:38 -0000 1.101
+++ mi-main.c 21 Aug 2007 13:26:30 -0000
@@ -1465,10 +1465,13 @@ mi_load_progress (const char *section_na
of this function. */
saved_uiout = uiout;
- if (current_interp_named_p (INTERP_MI))
+ if (current_interp_named_p (INTERP_MI)
+ || current_interp_named_p (INTERP_MI2))
uiout = mi_out_new (2);
else if (current_interp_named_p (INTERP_MI1))
uiout = mi_out_new (1);
+ else if (current_interp_named_p (INTERP_MI3))
+ uiout = mi_out_new (3);
else
return;
next prev parent reply other threads:[~2007-08-21 13:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-20 21:04 Maxim Grigoriev
2007-08-21 12:16 ` Nick Roberts
2007-08-21 13:28 ` Daniel Jacobowitz [this message]
2007-08-22 5:33 ` Nick Roberts
2007-08-22 11:09 ` Daniel Jacobowitz
2007-08-23 6:11 ` Nick Roberts
2007-08-23 11:48 ` Daniel Jacobowitz
2007-09-03 17:51 ` Daniel Jacobowitz
2007-08-21 17:43 ` Maxim Grigoriev
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=20070821132753.GA25612@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=marc@tensilica.com \
--cc=maxim@tensilica.com \
--cc=nickrob@snap.net.nz \
--cc=pmac@tensilica.com \
--cc=ross@tensilica.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