This is the mail archive of the
mailing list for the GDB project.
Re: MI output change
- From: Bob Rossi <bob at brasko dot net>
- To: Andrew Cagney <cagney at gnu dot org>
- Cc: gdb at sources dot redhat dot com
- Date: Fri, 14 Jan 2005 20:37:48 -0500
- Subject: Re: MI output change
- References: <41E8316F.firstname.lastname@example.org>
On Fri, Jan 14, 2005 at 03:54:07PM -0500, Andrew Cagney wrote:
> The MI output is currently littered with:
> PASS: gdb.mi/mi-var-cmd.exp: create lsimple->integer
> -var-create int * int
> &"Attempt to use a type name as an expression.\n"
> &"mi_cmd_var_create: unable to create variable object\n"
> ^error,msg="mi_cmd_var_create: unable to create variable object"
> (note how the error appears as both the result and as standard out)
> My recent exception handling rewrite means that this can finally be
> fixed. However that means that the MI output has technically changed -
> no one should be relying on the message appearing on stdout but hey ...
> Is this going to be an issue?
Seems like a nice improvement.
The message in "msg" does not have a newline, while the one after '&'
does. Does this matter at all?