From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30981 invoked by alias); 25 Jun 2007 18:04:41 -0000 Received: (qmail 30971 invoked by uid 22791); 25 Jun 2007 18:04:40 -0000 X-Spam-Check-By: sourceware.org Received: from mail-out3.apple.com (HELO mail-out3.apple.com) (17.254.13.22) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 25 Jun 2007 18:04:37 +0000 Received: from relay7.apple.com (relay7.apple.com [17.128.113.37]) by mail-out3.apple.com (Postfix) with ESMTP id E870DA33C67; Mon, 25 Jun 2007 11:04:28 -0700 (PDT) Received: from relay7.apple.com (unknown [127.0.0.1]) by relay7.apple.com (Symantec Mail Security) with ESMTP id D6F99300AE; Mon, 25 Jun 2007 11:04:28 -0700 (PDT) X-AuditID: 11807125-a446abb0000007df-ca-468003ac5141 Received: from gdbrulez.apple.com (int-si-a.apple.com [17.128.113.41]) by relay7.apple.com (Apple SCV relay) with ESMTP id C143130083; Mon, 25 Jun 2007 11:04:28 -0700 (PDT) Cc: kdevelop@kdevelop.org, Nick Roberts , gdb@sources.redhat.com Message-Id: From: Jim Ingham To: Vladimir Prus In-Reply-To: <200706251101.54544.ghost@cs.msu.su> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit X-Mailer: Apple Mail (2.891) Mime-Version: 1.0 (Apple Message framework v891) Subject: Re: 'continue' command problem Date: Mon, 25 Jun 2007 18:04:00 -0000 References: <200706041421.21962.leonp@plris.com> <200706251101.54544.ghost@cs.msu.su> 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/msg00244.txt.bz2 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. Jim On Jun 25, 2007, at 12:01 AM, Vladimir Prus wrote: > On Monday 04 June 2007 15:21, Leon Pollak wrote: > > [cross-posting to gdb-devel] > >> Hello. >> >> This is the message to Vladimir Prus (as the debugger interface >> maintainer): >> >> When the user defined gdb macro contains "continue" command inside, >> this >> causes the debugger interface to loose its head (BP hit, ball/ >> circle/point >> presentation and BP tab are in disorder). > > This is more or less expected. In this case GDB fails to inform us > that > the target started running, so we think it's stopped, and many bad > things > can happen. > > Nick, > I think your "async branch" is supposed to emit "^running" in all > possible cases. > Is that the case, and if so, do you think that improvement can be > ported to > gdb mainline quickly? > > - Volodya