From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5942 invoked by alias); 27 Jan 2006 20:04:46 -0000 Received: (qmail 5933 invoked by uid 22791); 27 Jan 2006 20:04:46 -0000 X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 27 Jan 2006 20:04:45 +0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.11/8.12.11) with ESMTP id k0RK4gDC001873; Fri, 27 Jan 2006 15:04:42 -0500 Received: from potter.sfbay.redhat.com (potter.sfbay.redhat.com [172.16.27.15]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id k0RK4Z112266; Fri, 27 Jan 2006 15:04:35 -0500 Received: from [172.16.24.50] (bluegiant.sfbay.redhat.com [172.16.24.50]) by potter.sfbay.redhat.com (8.12.8/8.12.8) with ESMTP id k0RK4UhD012691; Fri, 27 Jan 2006 15:04:31 -0500 Message-ID: <43DA7BFE.2070100@redhat.com> Date: Fri, 27 Jan 2006 20:04:00 -0000 From: Michael Snyder User-Agent: Mozilla Thunderbird 1.0.7-1.4.1 (X11/20050929) MIME-Version: 1.0 To: Daniel Jacobowitz CC: gdb-patches@sourceware.org Subject: Re: Some more multi-fork fixes References: <20060115190757.GA10454@nevyn.them.org> In-Reply-To: <20060115190757.GA10454@nevyn.them.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2006-01/txt/msg00454.txt.bz2 Daniel Jacobowitz wrote: > These patches allow multi-fork.exp to pass on x86_64-pc-linux-gnu, most of > the time. I'm sorry I didn't notice the _dl_sysinfo_int80 bit earlier. Thanks, I'd been thinking about that... > Some other problems I noticed, but did not fix: > > The "follow child, print pids" test is victim of a race condition; sometimes > the "$pid done" printout from the inferior will be interleaved with the GDB > output, causing expect to mark the test as a failure. > > delete-fork really ought to call waitpid after deleting the fork; otherwise > the process lives on as a zombie. That's fine with me too.