From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19235 invoked by alias); 3 Feb 2009 05:36:22 -0000 Received: (qmail 19226 invoked by uid 22791); 3 Feb 2009 05:36:21 -0000 X-SWARE-Spam-Status: No, hits=-1.7 required=5.0 tests=AWL,BAYES_00,SARE_MSGID_LONG40,SPF_PASS X-Spam-Check-By: sourceware.org Received: from ti-out-0910.google.com (HELO ti-out-0910.google.com) (209.85.142.188) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 03 Feb 2009 05:36:16 +0000 Received: by ti-out-0910.google.com with SMTP id d10so1040695tib.12 for ; Mon, 02 Feb 2009 21:36:14 -0800 (PST) MIME-Version: 1.0 Received: by 10.110.2.2 with SMTP id 2mr7845493tib.17.1233639374252; Mon, 02 Feb 2009 21:36:14 -0800 (PST) In-Reply-To: <6D19CA8D71C89C43A057926FE0D4ADAA06CB0F19@ecamlmw720.eamcs.ericsson.se> References: <6D19CA8D71C89C43A057926FE0D4ADAA06CB0F19@ecamlmw720.eamcs.ericsson.se> Date: Tue, 03 Feb 2009 05:36:00 -0000 Message-ID: Subject: Re: MI *stopped versus silent breakpoint From: teawater To: Marc Khouzam Cc: gdb@sourceware.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit 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: 2009-02/txt/msg00027.txt.bz2 Hi Marc, When I try reverse-debug with MI what I got is: (gdb) reverse-finish &"reverse-finish\n" ~"Run back to call of #0 cool () at 1.c:15\n" ^running *running,thread-id="all" (gdb) *stopped *running,thread-id="all" ~"main () at 1.c:25\n" ~"25\t b = cool ();\n" *stopped (gdb) Could you give me some example about what you talk about ? Thanks, Hui On Wed, Jan 21, 2009 at 23:41, Marc Khouzam wrote: > Hi, > > I just found out that a breakpoint can be made silent, in which case > there > is no breakpoint output when it is hit. When doing a reverse-finish > operation, a silent breakpoint is used, and when hit the inferior is > resumed > automatically, and then a single-step is done. > > In CLI, it makes it look like the inferior stopped only once, instead of > twice. > > In MI though, with the *stopped events, we do get an empty > *stopped for the silent breakpoint. So I see two *stopped events > consecutively. > > I wondered if a silent breakpoint should in fact generate a *stopped > event > or not? For a frontend, it can be confusing to see two stopped events. > FYI, what I did for DSF-GDB and reverse debugging, is to ignore empty > *stopped. > I stilled wondered about GDB though. > > Marc > > > > > > >