From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16506 invoked by alias); 26 Jun 2007 07:13:48 -0000 Received: (qmail 16496 invoked by uid 22791); 26 Jun 2007 07:13:47 -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.31) with ESMTP; Tue, 26 Jun 2007 07:13:43 +0000 Received: from list by ciao.gmane.org with local (Exim 4.43) id 1I35Eh-0003MA-Tw for gdb@sources.redhat.com; Tue, 26 Jun 2007 09:13:16 +0200 Received: from 77.246.241.246 ([77.246.241.246]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 26 Jun 2007 09:13:15 +0200 Received: from ghost by 77.246.241.246 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 26 Jun 2007 09:13:15 +0200 To: gdb@sources.redhat.com From: Vladimir Prus Subject: Re: 'continue' command problem Followup-To: gmane.comp.gdb.devel Date: Tue, 26 Jun 2007 07:13:00 -0000 Message-ID: References: <200706041421.21962.leonp@plris.com> <200706251101.54544.ghost@cs.msu.su> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7Bit User-Agent: KNode/0.10.2 Cc: kdevelop@kdevelop.org 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: 2007-06/txt/msg00291.txt.bz2 Jim Ingham wrote: > At Apple, we also added a "breakpoint-commands" output field to the > "*stopped - breakpoint-hit" message. Then we either tell it that the > breakpoint commands are done running, or that they have restarted the > target. That way the UI can know to suspend putting up some UI > (getting the current stack, etc) till it knows the target has stopped > for sure... After all, one very common use of breakpoint commands is > on the fly logging, in which case you do want to display whatever the > breakpoint command prints in your gdb console log window, but you > don't want to do anything else. Actually, the original bug report is not related to breakpoint commands. Now, gdb does not emit "^running" on any CLI commands at all -- like "continue", or "until". And when such commands are used inside gdb macro, we're completely out of luck. I'd imagine that "continue" used in breakpoint commands should also emit "^running", but I'm not sure about this part. - Volodya