From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6330 invoked by alias); 15 Dec 2008 06:46:18 -0000 Received: (qmail 6319 invoked by uid 22791); 15 Dec 2008 06:46:17 -0000 X-Spam-Check-By: sourceware.org Received: from main.gmane.org (HELO ciao.gmane.org) (80.91.229.2) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 15 Dec 2008 06:45:25 +0000 Received: from list by ciao.gmane.org with local (Exim 4.43) id 1LC7Cf-0002LP-MW for gdb@sources.redhat.com; Mon, 15 Dec 2008 06:45:17 +0000 Received: from 78.158.192.230 ([78.158.192.230]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 15 Dec 2008 06:45:17 +0000 Received: from vladimir by 78.158.192.230 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 15 Dec 2008 06:45:17 +0000 To: gdb@sources.redhat.com From: Vladimir Prus Subject: Re: MI *stopped event with CLI commands Date: Mon, 15 Dec 2008 06:46:00 -0000 Message-ID: References: <6D19CA8D71C89C43A057926FE0D4ADAA04E1BEC8@ecamlmw720.eamcs.ericsson.se> <18757.63035.269334.203651@kahikatea.snap.net.nz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7Bit User-Agent: KNode/0.10.9 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/msg00061.txt.bz2 Nick Roberts wrote: > > 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. Probably. Though it does not change the fact that *stopped without details sounds like a bug. I'll take a look, though it might take a few days. - Volodya