From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12723 invoked by alias); 30 Mar 2006 01:14:58 -0000 Received: (qmail 12715 invoked by uid 22791); 30 Mar 2006 01:14:58 -0000 X-Spam-Check-By: sourceware.org Received: from e34.co.us.ibm.com (HELO e34.co.us.ibm.com) (32.97.110.152) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 30 Mar 2006 01:14:56 +0000 Received: from d03relay04.boulder.ibm.com (d03relay04.boulder.ibm.com [9.17.195.106]) by e34.co.us.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id k2U1EtV7008635 for ; Wed, 29 Mar 2006 20:14:55 -0500 Received: from d03av02.boulder.ibm.com (d03av02.boulder.ibm.com [9.17.195.168]) by d03relay04.boulder.ibm.com (8.12.10/NCO/VER6.8) with ESMTP id k2U1I2Mk123600 for ; Wed, 29 Mar 2006 18:18:02 -0700 Received: from d03av02.boulder.ibm.com (loopback [127.0.0.1]) by d03av02.boulder.ibm.com (8.12.11/8.13.3) with ESMTP id k2U1Es8r023140 for ; Wed, 29 Mar 2006 18:14:54 -0700 Received: from dufur.beaverton.ibm.com (dufur.beaverton.ibm.com [9.47.22.20]) by d03av02.boulder.ibm.com (8.12.11/8.12.11) with ESMTP id k2U1Esr4023130 for ; Wed, 29 Mar 2006 18:14:54 -0700 Subject: GDB paper for GCC summit: New Commands From: PAUL GILLIAM Reply-To: pgilliam@us.ibm.com To: gdb@sources.redhat.com In-Reply-To: <1142633147.21920.400.camel@dufur.beaverton.ibm.com> References: <1142633147.21920.400.camel@dufur.beaverton.ibm.com> Content-Type: text/plain Date: Thu, 30 Mar 2006 01:36:00 -0000 Message-Id: <1143681561.21920.426.camel@dufur.beaverton.ibm.com> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2006-03/txt/msg00212.txt.bz2 Here is stuff about new commands I gleaned from NEWS. I have some questions at the end and would welcome any comments. (I intend to do new features separately from new commands and I know there will be some overlap). Feature: Checkpoints commands: checkpoint restart info checkpoints delete-checkpoint Feature: fork commands: set|show detach-on-fork info forks fork delete-fork detach-fork Feature: Convenience variables commands: init-if-undefined Feature: displaying arrays command: set print array-indexes Feature: logging output to a file command: set|show logging Other New Commands: start maint set profile on|off disconnect Removed Commands: removed replacement set|show arm dissembly-favor set|show arm disassembler othernames set arm disassembler set|show remotedebug set|show debug remote set|show archdebug set|show debug arch set|show eventdebug set|show debug event regs info registers set prompt-escape-char - none - Qustions: 1) How do "set|show detach-on-fork" and "set|show follow-fork" work together? I think this is the answer: If 'set detach-on-fork' is off, the 'set follow-fork' works as before. If 'set detach-on-fork' is on, then the state of 'set follow-fork' determines which for will be the 'current' fork. Is this correct? 2) Does the new fork features also work with vfork? If not, they are inconsistent with 'set|show follow-fork'. 3) If the name of the main procedure is 'main', is the start command equivalent to 'tbreak main' followed by 'run', or is there something subtle going on?