From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17374 invoked by alias); 8 Feb 2005 16:22:29 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 17330 invoked from network); 8 Feb 2005 16:22:23 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org with SMTP; 8 Feb 2005 16:22:23 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.11/8.12.11) with ESMTP id j18GMIYa030558 for ; Tue, 8 Feb 2005 11:22:23 -0500 Received: from localhost.redhat.com (vpn50-111.rdu.redhat.com [172.16.50.111]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id j18GMHO14910; Tue, 8 Feb 2005 11:22:17 -0500 Received: from [127.0.0.1] (localhost.localdomain [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 3BA9B7D79; Tue, 8 Feb 2005 11:21:48 -0500 (EST) Message-ID: <4208E71A.5070307@gnu.org> Date: Tue, 08 Feb 2005 16:30:00 -0000 From: Andrew Cagney User-Agent: Mozilla Thunderbird 0.8 (X11/20041020) MIME-Version: 1.0 To: Andrew Cagney Cc: gdb@sources.redhat.com Subject: Re: MI output change References: <41E8316F.7050806@gnu.org> In-Reply-To: <41E8316F.7050806@gnu.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2005-02/txt/msg00041.txt.bz2 Andrew Cagney wrote: Two ya's, no Na's. All but 'done' :-/ > Hello, > > The MI output is currently littered with: > > (gdb) > PASS: gdb.mi/mi-var-cmd.exp: create lsimple->integer > -var-create int * int > &"Attempt to use a type name as an expression.\n" > &"mi_cmd_var_create: unable to create variable object\n" > ^error,msg="mi_cmd_var_create: unable to create variable object" > (gdb) > > (note how the error appears as both the result and as standard out) > > My recent exception handling rewrite means that this can finally be > fixed. However that means that the MI output has technically changed - > no one should be relying on the message appearing on stdout but hey ... > > Is this going to be an issue? > > Andrew >