This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: cleanup mi error message handling
On Tue, Mar 25, 2008 at 01:28:26PM +1200, Nick Roberts wrote:
> > > Just as you say if the "frontend wants to display this error to the user
> > > in the console, it can do so anyway" isn't it equally true that if it
> > > doesn't want to display this error, it can choose not to so?
> >
> > Yes, but unlike a formatted MI response, the front end doesn't know
> > what a random bit of ~"output" is. It might be a notification, like a
> > new thread, or an error message, or...
>
> Errors aren't CONSOLE-STREAM-OUTPUT but LOG-STREAM-OUTPUT and are prefixed
> with `&' not `~':
>
> &"The program is not being run.\n"
> ^error,msg="The program is not being run."
> (gdb)
>
> =thread-created,id=2
> ~"[New Thread 0xb7568b90 (LWP 19810)]\n"
Whoops, you're right. Sorry for confusing the issue.
`"&" STRING-OUTPUT'
The log stream contains debugging messages being produced by GDB's
internals.
I still think that means we shouldn't be producing them for
errors.
--
Daniel Jacobowitz
CodeSourcery