From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16960 invoked by alias); 25 Mar 2008 02:12:39 -0000 Received: (qmail 16943 invoked by uid 22791); 25 Mar 2008 02:12:37 -0000 X-Spam-Check-By: sourceware.org Received: from NaN.false.org (HELO nan.false.org) (208.75.86.248) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 25 Mar 2008 02:12:18 +0000 Received: from nan.false.org (localhost [127.0.0.1]) by nan.false.org (Postfix) with ESMTP id DA59E983C6; Tue, 25 Mar 2008 02:12:15 +0000 (GMT) Received: from caradoc.them.org (22.svnf5.xdsl.nauticom.net [209.195.183.55]) by nan.false.org (Postfix) with ESMTP id BB6589810C; Tue, 25 Mar 2008 02:12:15 +0000 (GMT) Received: from drow by caradoc.them.org with local (Exim 4.69) (envelope-from ) id 1Jdye6-0008EE-SG; Mon, 24 Mar 2008 22:12:14 -0400 Date: Tue, 25 Mar 2008 02:12:00 -0000 From: Daniel Jacobowitz To: Nick Roberts Cc: Pedro Alves , gdb-patches@sourceware.org Subject: Re: cleanup mi error message handling Message-ID: <20080325021214.GA31594@caradoc.them.org> Mail-Followup-To: Nick Roberts , Pedro Alves , gdb-patches@sourceware.org References: <200803241830.11759.pedro@codesourcery.com> <18408.9553.683746.929167@kahikatea.snap.net.nz> <20080324223840.GA20307@caradoc.them.org> <18408.15132.721049.31408@kahikatea.snap.net.nz> <20080325005941.GA27677@caradoc.them.org> <18408.21818.695835.725321@kahikatea.snap.net.nz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <18408.21818.695835.725321@kahikatea.snap.net.nz> User-Agent: Mutt/1.5.17 (2007-12-11) 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-03/txt/msg00376.txt.bz2 On Tue, Mar 25, 2008 at 01:28:26PM +1200, Nick Roberts wrote: > > > Just as you say if the "frontend wants to display this error to the user > > > in the console, it can do so anyway" isn't it equally true that if it > > > doesn't want to display this error, it can choose not to so? > > > > Yes, but unlike a formatted MI response, the front end doesn't know > > what a random bit of ~"output" is. It might be a notification, like a > > new thread, or an error message, or... > > Errors aren't CONSOLE-STREAM-OUTPUT but LOG-STREAM-OUTPUT and are prefixed > with `&' not `~': > > &"The program is not being run.\n" > ^error,msg="The program is not being run." > (gdb) > > =thread-created,id=2 > ~"[New Thread 0xb7568b90 (LWP 19810)]\n" Whoops, you're right. Sorry for confusing the issue. `"&" STRING-OUTPUT' The log stream contains debugging messages being produced by GDB's internals. I still think that means we shouldn't be producing them for errors. -- Daniel Jacobowitz CodeSourcery