From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15438 invoked by alias); 5 Sep 2007 05:24:05 -0000 Received: (qmail 15429 invoked by uid 22791); 5 Sep 2007 05:24:03 -0000 X-Spam-Check-By: sourceware.org Received: from viper.snap.net.nz (HELO viper.snap.net.nz) (202.37.101.8) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 05 Sep 2007 05:23:57 +0000 Received: from kahikatea.snap.net.nz (153.61.255.123.dynamic.snap.net.nz [123.255.61.153]) by viper.snap.net.nz (Postfix) with ESMTP id EBB253D9F2D; Wed, 5 Sep 2007 17:23:53 +1200 (NZST) Received: by kahikatea.snap.net.nz (Postfix, from userid 1000) id B4E518FC6D; Wed, 5 Sep 2007 17:23:52 +1200 (NZST) From: Nick Roberts MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <18142.15716.179444.106490@kahikatea.snap.net.nz> Date: Wed, 05 Sep 2007 05:24:00 -0000 To: Vladimir Prus Cc: gdb@sources.redhat.com Subject: Re: MI: "^running" issues In-Reply-To: <200709041653.22357.ghost@cs.msu.su> References: <200709041653.22357.ghost@cs.msu.su> X-Mailer: VM 7.19 under Emacs 23.0.50.4 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-09/txt/msg00028.txt.bz2 > I've just run into a somewhat nasty behaviour of gdb. > Suppose if you've set 5 hardware watchpoints (on x86) > and to -exec-step. The output from gdb will be: > > (gdb) -exec-next > ^running > (gdb) > 34^error,msg="...." I can't reproduce this. It looks like partial recipe. >... > - Killing the idea of async commands. It does not seem to be very useful > at this point, so we might be better off ripping it and implementing afresh > later, when it's understood what they should be. I'm working in the opposite direction: trying to get GDB to work asynchronously. I don't see the point of ripping out what is already there. -- Nick http://www.inet.net.nz/~nickrob