From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8490 invoked by alias); 4 Mar 2005 11:23:11 -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 8422 invoked from network); 4 Mar 2005 11:23:02 -0000 Received: from unknown (HELO lakermmtao10.cox.net) (68.230.240.29) by sourceware.org with SMTP; 4 Mar 2005 11:23:02 -0000 Received: from white ([68.9.64.121]) by lakermmtao10.cox.net (InterMail vM.6.01.04.00 201-2131-118-20041027) with ESMTP id <20050304112302.SBVX29924.lakermmtao10.cox.net@white>; Fri, 4 Mar 2005 06:23:02 -0500 Received: from bob by white with local (Exim 3.35 #1 (Debian)) id 1D7Atd-0000Wc-00; Fri, 04 Mar 2005 06:23:05 -0500 Date: Fri, 04 Mar 2005 11:23:00 -0000 From: Bob Rossi To: Nick Roberts Cc: Andrew Cagney , gdb@sources.redhat.com Subject: Re: fullname descriptor with -break-list Message-ID: <20050304112305.GA1471@white> Mail-Followup-To: Nick Roberts , Andrew Cagney , gdb@sources.redhat.com References: <16902.30786.705993.121669@farnswood.snap.net.nz> <20050206210637.GB19609@white> <16902.45534.858929.941689@farnswood.snap.net.nz> <20050207134829.GA21985@white> <420787A3.2070605@gnu.org> <16936.3238.730574.794373@farnswood.snap.net.nz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <16936.3238.730574.794373@farnswood.snap.net.nz> User-Agent: Mutt/1.3.28i X-SW-Source: 2005-03/txt/msg00033.txt.bz2 On Fri, Mar 04, 2005 at 08:22:14PM +1300, Nick Roberts wrote: > > >>-exec-run > > >>^running > > >>(gdb) > > >>*stopped,reason="breakpoint-hit",bkptno="1",thread-id="0",frame={addr="0x080486e2",func="myprint",args=[{name="i",value="0"},{name="j",value="0"}],file="myprint.c",line="5"} > ... > > The way that message is generated is a massive kludge - so the > > underlying code could do with a cleanup - separate the code determining > > why the process stopped from the code printing the stop reason. > > Just a short note for the future: > > As *stopped is asynchronous output and not that of a specific MI command, I > also think this output should appear even if a CLI command has been invoked. If you are refering to the fact that you want to know what MI output command is being sent to you when the command is asynchronous, I completly agree. In fact, I have plans, if accepted, to put the type of MI output command directly into the MI output command. The Apple guys said they patched GDB to behave like this, but only for asynchronous commands. Bob Rossi