From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22958 invoked by alias); 15 Dec 2008 04:20:45 -0000 Received: (qmail 22930 invoked by uid 22791); 15 Dec 2008 04:20:42 -0000 X-Spam-Check-By: sourceware.org Received: from imr2.ericy.com (HELO imr2.ericy.com) (198.24.6.3) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 15 Dec 2008 04:19:48 +0000 Received: from eusrcmw751.eamcs.ericsson.se (eusrcmw751.exu.ericsson.se [138.85.77.51]) by imr2.ericy.com (8.13.1/8.13.1) with ESMTP id mBF4JjKV016053 for ; Sun, 14 Dec 2008 22:19:46 -0600 Received: from ecamlmw720.eamcs.ericsson.se ([142.133.1.72]) by eusrcmw751.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Sun, 14 Dec 2008 22:19:45 -0600 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: MI *stopped event with CLI commands Date: Mon, 15 Dec 2008 04:20:00 -0000 Message-ID: <6D19CA8D71C89C43A057926FE0D4ADAA04E1BEC8@ecamlmw720.eamcs.ericsson.se> From: "Marc Khouzam" To: 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/msg00058.txt.bz2 Hi, with the latest MI changes, when running in MI mode, a *stopped event is is= sued 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=3D"breakpoint-hit",disp=3D"keep",bkptno=3D"1",thread-id=3D"= 1", stopped-threads=3D"all",frame=3D{addr=3D"0x08048415",func=3D"main",args=3D[= ],file=3D"c.cc",fullname=3D"c.cc",line=3D"5"} Was this intended? And if so, what should a frontend do in this case?=20=20 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 havi= ng=20 the *stopped event after CLI commands. Wouldn't be nice if the stopped event always had the full information? Thanks Marc