From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21012 invoked by alias); 1 Nov 2008 23:05:06 -0000 Received: (qmail 20855 invoked by uid 22791); 1 Nov 2008 23:05:04 -0000 X-Spam-Check-By: sourceware.org Received: from viper.snap.net.nz (HELO viper.snap.net.nz) (202.37.101.25) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sat, 01 Nov 2008 23:04:08 +0000 Received: from kahikatea.snap.net.nz (219.31.255.123.static.snap.net.nz [123.255.31.219]) by viper.snap.net.nz (Postfix) with ESMTP id 981D43DA1AE for ; Sun, 2 Nov 2008 12:04:04 +1300 (NZDT) Received: by kahikatea.snap.net.nz (Postfix, from userid 1000) id 3E0578FC6D; Sun, 2 Nov 2008 12:03:56 +1300 (NZDT) From: Nick Roberts MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <18700.57435.636298.708472@kahikatea.snap.net.nz> Date: Sat, 01 Nov 2008 23:05:00 -0000 To: gdb@sourceware.org Subject: Documentation issues X-Mailer: VM 7.19 under Emacs 22.3.1 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: 2008-11/txt/msg00005.txt.bz2 The followin commands are still mentioned in the manual but appear to have been removed (replaced by target-async?): `maint set linux-async' `maint show linux-async' Control the GNU/Linux native asynchronous support (*note Background Execution::) of GDB. GNU/Linux native asynchronous support will be disabled until you use the `maint set linux-async' command to enable it. `maint set remote-async' `maint show remote-async' Control the remote asynchronous support (*note Background Execution::) of GDB. Remote asynchronous support will be disabled until you use the `maint set remote-async' command to enable it. `set target-async' is mentioned but not described as a boolean command. The manual says: The MI execution commands (*note GDB/MI Program Execution::) are always executed asynchronously in non-stop mode. That does not appear to be true. It seems that you need to set target-async in this case too. Many MI commands accept the options "--thread" and "--frame" now but I can see no mention of this in the manual. The MI commands "-exec-interrupt" and "-exec-continue" accept "--all" and this is not mentioned either. In MI, the async record *stopped always generates a "stopped-threads" field but this is neither described nor displayed any of the examples showing *stopped output in the manual. -- Nick http://www.inet.net.nz/~nickrob