* MI output change
@ 2005-01-14 20:56 Andrew Cagney
2005-01-15 1:37 ` Bob Rossi
2005-02-08 16:30 ` Andrew Cagney
0 siblings, 2 replies; 4+ messages in thread
From: Andrew Cagney @ 2005-01-14 20:56 UTC (permalink / raw)
To: gdb
Hello,
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
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: MI output change
2005-01-14 20:56 MI output change Andrew Cagney
@ 2005-01-15 1:37 ` Bob Rossi
2005-02-08 16:30 ` Andrew Cagney
1 sibling, 0 replies; 4+ messages in thread
From: Bob Rossi @ 2005-01-15 1:37 UTC (permalink / raw)
To: Andrew Cagney; +Cc: gdb
On Fri, Jan 14, 2005 at 03:54:07PM -0500, Andrew Cagney wrote:
> Hello,
>
> 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?
Seems like a nice improvement.
The message in "msg" does not have a newline, while the one after '&'
does. Does this matter at all?
Bob Rossi
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: MI output change
2005-01-14 20:56 MI output change Andrew Cagney
2005-01-15 1:37 ` Bob Rossi
@ 2005-02-08 16:30 ` Andrew Cagney
2005-02-09 4:51 ` Bob Rossi
1 sibling, 1 reply; 4+ messages in thread
From: Andrew Cagney @ 2005-02-08 16:30 UTC (permalink / raw)
To: Andrew Cagney; +Cc: gdb
Andrew Cagney wrote:
Two ya's, no Na's. All but 'done' :-/
> Hello,
>
> 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
>
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: MI output change
2005-02-08 16:30 ` Andrew Cagney
@ 2005-02-09 4:51 ` Bob Rossi
0 siblings, 0 replies; 4+ messages in thread
From: Bob Rossi @ 2005-02-09 4:51 UTC (permalink / raw)
To: Andrew Cagney, g; +Cc: gdb
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
> >
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2005-02-09 2:33 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2005-01-14 20:56 MI output change Andrew Cagney
2005-01-15 1:37 ` Bob Rossi
2005-02-08 16:30 ` Andrew Cagney
2005-02-09 4:51 ` Bob Rossi
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).