From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26915 invoked by alias); 12 Feb 2006 20:49:26 -0000 Received: (qmail 26904 invoked by uid 22791); 12 Feb 2006 20:49:25 -0000 X-Spam-Check-By: sourceware.org Received: from viper.snap.net.nz (HELO viper.snap.net.nz) (202.37.101.8) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sun, 12 Feb 2006 20:49:21 +0000 Received: from kahikatea.snap.net.nz (p202-124-115-182.snap.net.nz [202.124.115.182]) by viper.snap.net.nz (Postfix) with ESMTP id 822DB744F13; Mon, 13 Feb 2006 09:49:15 +1300 (NZDT) Received: by kahikatea.snap.net.nz (Postfix, from userid 500) id EA14F8890; Mon, 13 Feb 2006 09:48:18 +1300 (NZDT) From: Nick Roberts MIME-Version: 1.0 Content-Type: text/plain; charset=unknown Content-Transfer-Encoding: quoted-printable Message-ID: <17391.40721.926885.140030@kahikatea.snap.net.nz> Date: Sun, 12 Feb 2006 20:49:00 -0000 To: "Bjarke Viksoe" Cc: gdb@sourceware.org Subject: MI error msgs and localization In-Reply-To: References: X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2006-02/txt/msg00120.txt.bz2 > Hi, I've been using the MI interface for quite some time and noticed tha= t=20 > preparation for localization has begun in GDB. Can I express some concer= n=20 > that compatibility with existing MI systems may suffer from this. AFAIK, the only localisation proposed for MI output is for error messages. > For instance, a cleanup must be done to make sure all errors are still=20 > reported through MI in English =96 including the more exceptional ones=20 > (especially during startup). For instance, I am actively interpreting ra= w=20 > console-stream output for the following strings: >=20 > No debugging symbols found > Unable to attach to process > No such process > No symbol table is loaded > No such file > gdb: unrecognized option > An internal GDB error was detected. > Thread x has terminated. > No executable file specified > No executable specified, use=85 These messages appear to be part of the CLI output intended for the user and not MI. It seems natural to translate them. > For yet-unsupported commands in MI I resort to =93-interpreter-exec cons= ole=20 > xxx=94, but that leaves a problem where I have to at least handle messag= es=20 > such as >=20 > ---Type =85 >=20 > =85to keep the non-interactive experience a joy. You can do "-gdb-set height 0" to stop this. Patches are welcome for any further MI commands that you would like to see implemented. > Please consider support for MI as an important feature in future version= s of=20 > GDB as well. English MI error output should somehow be retained for Mach= ine=20 > Interpreting (!!) perhaps with the additional inclusion of the localized= =20 > display text. As stated in the manual, MI is still evolving. The best way to make it do the things you want is to participate in its development. Nick http://www.inet.net.nz/~nick= rob