From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22944 invoked by alias); 7 Jul 2009 15:52:40 -0000 Received: (qmail 22936 invoked by uid 22791); 7 Jul 2009 15:52:40 -0000 X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from NaN.false.org (HELO nan.false.org) (208.75.86.248) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 07 Jul 2009 15:52:34 +0000 Received: from nan.false.org (localhost [127.0.0.1]) by nan.false.org (Postfix) with ESMTP id 4F195108CB; Tue, 7 Jul 2009 15:52:32 +0000 (GMT) Received: from caradoc.them.org (209.195.188.212.nauticom.net [209.195.188.212]) by nan.false.org (Postfix) with ESMTP id DE166104AB; Tue, 7 Jul 2009 15:52:31 +0000 (GMT) Received: from drow by caradoc.them.org with local (Exim 4.69) (envelope-from ) id 1MOCy5-0006o6-U0; Tue, 07 Jul 2009 11:52:29 -0400 Date: Tue, 07 Jul 2009 15:52:00 -0000 From: Daniel Jacobowitz To: gdb@sourceware.org Cc: Eli Zaretskii , Pedro Alves Subject: NEWS entries Message-ID: <20090707155225.GA24199@caradoc.them.org> Mail-Followup-To: gdb@sourceware.org, Eli Zaretskii , Pedro Alves MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.20 (2009-06-14) 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/msg00047.txt.bz2 I have twice recently written release notes based on GDB's NEWS file. I noticed two related items which are documented, but IMO should be improved. I look through NEWS to know what cool things I (or my users) can try out, so I would like to know where they're expected to work. * 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. -- Daniel Jacobowitz CodeSourcery