This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: MI error messages
- From: Daniel Jacobowitz <drow at false dot org>
- To: Eli Zaretskii <eliz at gnu dot org>
- Cc: Vladimir Prus <ghost at cs dot msu dot su>, gdb at sources dot redhat dot com
- Date: Fri, 10 Feb 2006 08:47:01 -0500
- Subject: Re: MI error messages
- References: <dshtpc$frg$1@sea.gmane.org> <ulkwj2zvj.fsf@gnu.org>
On Fri, Feb 10, 2006 at 01:54:08PM +0200, Eli Zaretskii wrote:
> > From: Vladimir Prus <ghost@cs.msu.su>
> > Date: Fri, 10 Feb 2006 14:35:08 +0300
> >
> > 1. Is it guaranteed that all MI error message start with function name and a
> > semicolon?
>
> I see a small number of error messages that don't, but those are
> probably bugs that need to be fixed.
Really? Why? I don't think the function name adds much value in
user-level error messages. Internal errors, sure.
It is certainly not guaranteed; there's no separation between "MI error
messages" and "other GDB error messages" since an MI session can
reach just about any call to error() in the sources.
--
Daniel Jacobowitz
CodeSourcery