From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11931 invoked by alias); 30 Jun 2008 18:18:06 -0000 Received: (qmail 11923 invoked by uid 22791); 30 Jun 2008 18:18:05 -0000 X-Spam-Check-By: sourceware.org Received: from bluesmobile.specifix.com (HELO bluesmobile.specifix.com) (216.129.118.140) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 30 Jun 2008 18:17:09 +0000 Received: from [127.0.0.1] (bluesmobile.specifix.com [216.129.118.140]) by bluesmobile.specifix.com (Postfix) with ESMTP id 4CD4B3BF30; Mon, 30 Jun 2008 11:17:08 -0700 (PDT) Subject: Re: [MI non-stop 04/11] Implement --thread and --frame. From: Michael Snyder To: Eli Zaretskii Cc: Vladimir Prus , gdb-patches@sources.redhat.com In-Reply-To: References: <200806282044.14246.vladimir@codesourcery.com> Content-Type: text/plain Date: Mon, 30 Jun 2008 18:35:00 -0000 Message-Id: <1214849828.3601.1513.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.10.3 (2.10.3-7.fc7) Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2008-06/txt/msg00593.txt.bz2 On Sat, 2008-06-28 at 21:16 +0300, Eli Zaretskii wrote: > > From: Vladimir Prus > > > 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.