From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26379 invoked by alias); 6 Jul 2004 19:14:53 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 26032 invoked from network); 6 Jul 2004 19:14:49 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org with SMTP; 6 Jul 2004 19:14:49 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.10/8.12.10) with ESMTP id i66JEne3013619 for ; Tue, 6 Jul 2004 15:14:49 -0400 Received: from localhost.redhat.com (porkchop.devel.redhat.com [172.16.58.2]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id i66JEm023885; Tue, 6 Jul 2004 15:14:48 -0400 Received: from gnu.org (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id C04DC2B9D; Tue, 6 Jul 2004 15:14:36 -0400 (EDT) Message-ID: <40EAFA1C.7020108@gnu.org> Date: Tue, 06 Jul 2004 19:14:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-GB; rv:1.4.1) Gecko/20040217 MIME-Version: 1.0 To: Michael Elizabeth Chastain Cc: gdb@sources.redhat.com Subject: Re: gdb 6.2 blockers References: <20040706182423.393F34B104@berman.michael-chastain.com> In-Reply-To: <20040706182423.393F34B104@berman.michael-chastain.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2004-07/txt/msg00047.txt.bz2 > ac> - 1650 is an issue, but even there I'm wondering how much. It's ticking > ac> a horrible nasty race condition and may not be a real problem in the > ac> field - do people really run 100 thread programs using linuxthreads. > > 1650, manythreads.exp, works every time with gdb 6.1.1. > So if there's a kernel race condition then gdb does not trigger it > and gdb HEAD does. This is a user-visible regression. BTW, I did try to reproduce this bug. Mainline GDB and manythreads.exp appear to work everytime on NPTL based FC2 and RHEL2 GNU/Linux systems (well at least for the 30+ test runs I tried). That wasn't the case with 6.1. We should probably mention this fix in the NEWS file, and the apparent linuxthreads regression in PROBLEMS. Andrew