From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15179 invoked by alias); 12 Feb 2006 14:54:26 -0000 Received: (qmail 15171 invoked by uid 22791); 12 Feb 2006 14:54:25 -0000 X-Spam-Check-By: sourceware.org Received: from bay111-f17.bay111.hotmail.com (HELO hotmail.com) (64.4.17.27) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sun, 12 Feb 2006 14:54:24 +0000 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Sun, 12 Feb 2006 06:54:23 -0800 Message-ID: Received: from 64.4.17.200 by by111fd.bay111.hotmail.msn.com with HTTP; Sun, 12 Feb 2006 14:54:23 GMT X-Sender: bviksoe@hotmail.com From: "Bjarke Viksoe" To: gdb@sourceware.org Bcc: Subject: MI error msgs and localization Date: Sun, 12 Feb 2006 14:54:00 -0000 Mime-Version: 1.0 Content-Type: text/plain; format=flowed 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/msg00119.txt.bz2 Hi, I've been using the MI interface for quite some time and noticed that preparation for localization has begun in GDB. Can I express some concern that compatibility with existing MI systems may suffer from this. For instance, a cleanup must be done to make sure all errors are still reported through MI in English – including the more exceptional ones (especially during startup). For instance, I am actively interpreting raw console-stream output for the following strings: 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… For yet-unsupported commands in MI I resort to “-interpreter-exec console xxx”, but that leaves a problem where I have to at least handle messages such as ---Type … …to keep the non-interactive experience a joy. Please consider support for MI as an important feature in future versions of GDB as well. English MI error output should somehow be retained for Machine Interpreting (!!) perhaps with the additional inclusion of the localized display text. Regards bjarke BVRDE - http://bvrde.sourceforge.net/