This is the mail archive of the
gdb@sources.redhat.com
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>, g at white
- Cc: gdb at sources dot redhat dot com
- Date: Tue, 8 Feb 2005 21:33:08 -0500
- Subject: Re: MI output change
- References: <41E8316F.7050806@gnu.org> <4208E71A.5070307@gnu.org>
On Tue, Feb 08, 2005 at 11:21:46AM -0500, Andrew Cagney wrote:
> Andrew Cagney wrote:
> Two ya's, no Na's. All but 'done' :-/
> >Hello,
Has this patch been committed yet? The last failing MI testcase I have
in the syntax checked MI testsuite is one related to this problem.
If you've committed the change for this, I still have an example that
behaves as below.
Bob Rossi
> >The MI output is currently littered with:
> >
> >(gdb)
> >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"
> >(gdb)
> >
> >(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?
> >
> >Andrew
> >