This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [MI non-stop 04/11] Implement --thread and --frame.


On Sat, 2008-06-28 at 21:16 +0300, Eli Zaretskii wrote:
> > From:  Vladimir Prus <vladimir@codesourcery.com>

> > > MI commands are invoked by a program, so error messages 
> > > we generate should be understandable by a program, which probably
> > > means they should not be translated.
> > 
> > It's a bit questionable. For example, the error you mention above
> > is clearly a bug in frontend. Presenting a translated version of
> > that message to the user is essentially pointless. On the other
> > hand, "Thread is running", or "Memory not accessible" messages
> > can be helpful for users. Do we need two error messages, maybe?
> 
> Maybe.  Do front ends show the error messages to the user, or do they
> act on them themselves (or both)?

I usually stay out of MI discussions, 'cause I'm not
well informed, but...

If the error messages could be made a part of the spec, 
then the front end could do its own translating.




Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]