From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8947 invoked by alias); 25 Apr 2006 20:58:03 -0000 Received: (qmail 8939 invoked by uid 22791); 25 Apr 2006 20:58:02 -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; Tue, 25 Apr 2006 20:58:00 +0000 Received: from farnswood.snap.net.nz (p202-124-114-253.snap.net.nz [202.124.114.253]) by viper.snap.net.nz (Postfix) with ESMTP id 2684D754034; Wed, 26 Apr 2006 08:57:57 +1200 (NZST) Received: by farnswood.snap.net.nz (Postfix, from userid 500) id 051B562A99; Tue, 25 Apr 2006 21:58:04 +0100 (BST) From: Nick Roberts MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17486.36188.127822.347550@farnswood.snap.net.nz> Date: Wed, 26 Apr 2006 12:36:00 -0000 To: Daniel Jacobowitz Cc: gdb@sources.redhat.com Subject: Re: RFC: MI output during program execution In-Reply-To: <20060404220637.GA12064@nevyn.them.org> References: <17458.60694.135878.624750@farnswood.snap.net.nz> <20060404220637.GA12064@nevyn.them.org> X-Mailer: VM 7.19 under Emacs 22.0.50.40 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-04/txt/msg00313.txt.bz2 > > The async code used a heavily changed version of child_wait (in > > linux-nat.c). > > > > What does the new code use in place of this procedure? > > child_wait only ever worked for single-threaded executables. Now > linux_nat_wait is used, for both single-threaded and multi-threaded > executables. OK I follow that now and have moved the relevant async code from child_wait to linux_nat_wait. I've also re-instated the --async option so that --noasync *should* run as on the trunk. You said earlier that I'm free to create my own branch but since I've not done that before for GDB I think its sensible to run this past you first. Having read the node Versions and Branches in the GDB Inernals manual I propose to: 1) Create a branchpoint of current HEAD for gdb+dejagnu: cvs rtag nickrob-200604026-branchpoint gdb+dejagnu 2) Create a branch from that branchpoint: cvs rtag -b -r nickrob-200604026-branchpoint nickrob-200604026-branch \ gdb+dejagnu 3) Update my working directory to that branch: cvs update -r nickrob-200604026-branch 4) Add files called ChangeLog-async, README-async, TODO-async. 5) Modify version.in appropriately. 5) Commit my/Apple's changes. 6) Post those changes to gdb-patches. 7) Do regular merges with trunk: cvs update -j HEAD (?) When I've got this far I'll also explain what the code does and what I would like it to do in the future (from README-async) on the gdb mailing list. -- Nick http://www.inet.net.nz/~nickrob