From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26460 invoked by alias); 7 Jul 2009 19:23:05 -0000 Received: (qmail 26440 invoked by uid 22791); 7 Jul 2009 19:23:04 -0000 X-SWARE-Spam-Status: No, hits=0.4 required=5.0 tests=AWL,BAYES_00,RCVD_IN_JMF_BL,SPF_SOFTFAIL X-Spam-Check-By: sourceware.org Received: from mtaout7.012.net.il (HELO mtaout7.012.net.il) (84.95.2.19) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 07 Jul 2009 19:22:57 +0000 Received: from conversion-daemon.i-mtaout7.012.net.il by i-mtaout7.012.net.il (HyperSendmail v2007.08) id <0KMF00I00ESU8J00@i-mtaout7.012.net.il> for gdb@sourceware.org; Tue, 07 Jul 2009 22:22:31 +0300 (IDT) Received: from HOME-C4E4A596F7 ([77.126.249.41]) by i-mtaout7.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0KMF006YRF5IJK90@i-mtaout7.012.net.il>; Tue, 07 Jul 2009 22:22:31 +0300 (IDT) Date: Tue, 07 Jul 2009 19:23:00 -0000 From: Eli Zaretskii Subject: Re: NEWS entries In-reply-to: <20090707155225.GA24199@caradoc.them.org> To: Daniel Jacobowitz Cc: gdb@sourceware.org, pedro@codesourcery.com Reply-to: Eli Zaretskii Message-id: <83tz1oz4aw.fsf@gnu.org> References: <20090707155225.GA24199@caradoc.them.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: 2009-07/txt/msg00050.txt.bz2 > Date: Tue, 7 Jul 2009 11:52:29 -0400 > From: Daniel Jacobowitz > Cc: Eli Zaretskii , Pedro Alves > > * Process record and replay > > In a architecture environment that supports ``process record and > replay'', ``process record and replay'' target can record a log of > the process execution, and replay it with both forward and reverse > execute commands. > > I believe this is currently only supported on i386-linux, is that right? > If so, we should say so. Also, "execution commands". > > set non-stop > show non-stop > Control whether other threads are stopped or not when some thread hits > a breakpoint. > > Documenting "set non-stop" is fine - but can we get some text about > non-stop mode, itself? As above, this should include which platforms > non-stop is initially supported on. You are right on both counts. Patches are welcome, or I will do it eventually.