From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24496 invoked by alias); 21 Jun 2005 21:59:08 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 24487 invoked by uid 22791); 21 Jun 2005 21:59:05 -0000 Received: from mail-out4.apple.com (HELO mail-out4.apple.com) (17.254.13.23) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Tue, 21 Jun 2005 21:59:05 +0000 Received: from mailgate1.apple.com (a17-128-100-225.apple.com [17.128.100.225]) by mail-out4.apple.com (8.12.11/8.12.11) with ESMTP id j5LLx3Jv018385 for ; Tue, 21 Jun 2005 14:59:03 -0700 (PDT) Received: from relay4.apple.com (relay4.apple.com) by mailgate1.apple.com (Content Technologies SMTPRS 4.3.17) with ESMTP id ; Tue, 21 Jun 2005 14:59:03 -0700 Received: from [17.201.22.21] (moleja.apple.com [17.201.22.21]) by relay4.apple.com (8.12.11/8.12.11) with ESMTP id j5LLx11c026932; Tue, 21 Jun 2005 14:59:01 -0700 (PDT) In-Reply-To: <17080.35377.519988.619664@farnswood.snap.net.nz> References: <17075.57612.684597.392526@farnswood.snap.net.nz> <20050618155742.GB3663@nevyn.them.org> <17076.42233.730605.834264@farnswood.snap.net.nz> <20050618232032.GA28368@nevyn.them.org> <17076.59646.873454.551250@farnswood.snap.net.nz> <20050619145612.GA8219@nevyn.them.org> <17077.61587.164352.664225@farnswood.snap.net.nz> <17078.19977.660644.9978@farnswood.snap.net.nz> <20050620135108.GA29453@nevyn.them.org> <17079.14386.484824.134375@farnswood.snap.net.nz> <17079.57494.321274.96102@farnswood.snap.net.nz> <17080.35377.519988.619664@farnswood.snap.net.nz> Mime-Version: 1.0 (Apple Message framework v728) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <4B2E0CF3-987A-41E8-A2B3-0ADD6955DAF7@apple.com> Cc: Eli Zaretskii , gdb-patches@sources.redhat.com Content-Transfer-Encoding: 7bit From: Jason Molenda Subject: Re: [PATCH] MI error messages Date: Tue, 21 Jun 2005 21:59:00 -0000 To: Nick Roberts X-SW-Source: 2005-06/txt/msg00338.txt.bz2 On Jun 21, 2005, at 2:44 PM, Nick Roberts wrote: > I presumed mi_usage_error would call error. That way the error is > caught and > any cleanups and rewinds are done. However, you are right, it > would be nicer > just to get: > > (gdb) > -stack-select-frame > Usage: FRAME_SPEC. > (gdb) > > instead of > > (gdb) > -stack-select-frame > &"Usage: -stack-select-frame FRAME_SPEC\n" > ^error,msg="Usage: -stack-select-frame FRAME_SPEC" > (gdb) > > as these errors aren't intended for the user when the frontend is > being used. Yeah, we came to the same decision at Apple. When you throw error() while in MI mode, you only get the ^error message, you don't get the console-style &"..." with the same message. Our GUI has a little status line at the bottom of the window where it shows the error message, and if you have the "gdb console" window open, it shows the error text in a different color to differentiate the error message. It makes sense to let the GUI show the error in whatever way is most appropriate for it, instead of blotting back plain old text. J