From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28904 invoked by alias); 15 Dec 2008 06:17:39 -0000 Received: (qmail 28895 invoked by uid 22791); 15 Dec 2008 06:17:38 -0000 X-Spam-Check-By: sourceware.org Received: from viper.snap.net.nz (HELO viper.snap.net.nz) (202.37.101.23) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 15 Dec 2008 06:16:37 +0000 Received: from kahikatea.snap.net.nz (132.63.255.123.dynamic.snap.net.nz [123.255.63.132]) by viper.snap.net.nz (Postfix) with ESMTP id BE6713DA83D; Mon, 15 Dec 2008 19:16:34 +1300 (NZDT) Received: by kahikatea.snap.net.nz (Postfix, from userid 1000) id D956D8FC6D; Mon, 15 Dec 2008 19:16:28 +1300 (NZDT) From: Nick Roberts MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <18757.63035.269334.203651@kahikatea.snap.net.nz> Date: Mon, 15 Dec 2008 06:17:00 -0000 To: "Marc Khouzam" Cc: Subject: Re: MI *stopped event with CLI commands In-Reply-To: <6D19CA8D71C89C43A057926FE0D4ADAA04E1BEC8@ecamlmw720.eamcs.ericsson.se> References: <6D19CA8D71C89C43A057926FE0D4ADAA04E1BEC8@ecamlmw720.eamcs.ericsson.se> X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2008-12/txt/msg00059.txt.bz2 > with the latest MI changes, when running in MI mode, a *stopped event is issued whenever > the inferior stops, even if the last command was a CLI command. > However, the stopped event is bare if the command is a CLI command. > > *stopped > instead of > *stopped,reason="breakpoint-hit",disp="keep",bkptno="1",thread-id="1", > stopped-threads="all",frame={addr="0x08048415",func="main",args=[],file="c.cc",fullname="c.cc",line="5"} > > Was this intended? And if so, what should a frontend do in this case? > We can parse the CLI output or send MI commands to get the info... > However, it seems to me that having to do that, defeats the purpose of having > the *stopped event after CLI commands. > > Wouldn't be nice if the stopped event always had the full information? If you do: set target-async on first, you do get the full information. Perhaps this should be the default for targets which can run asynchronously. -- Nick http://www.inet.net.nz/~nickrob