From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30435 invoked by alias); 6 Jul 2004 20:03:46 -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 30425 invoked from network); 6 Jul 2004 20:03:45 -0000 Received: from unknown (HELO maynard.mail.mindspring.net) (207.69.200.243) by sourceware.org with SMTP; 6 Jul 2004 20:03:45 -0000 Received: from user-119a90a.biz.mindspring.com ([66.149.36.10] helo=berman.michael-chastain.com) by maynard.mail.mindspring.net with esmtp (Exim 3.33 #1) id 1BhwAK-0002qW-00; Tue, 06 Jul 2004 16:03:44 -0400 Received: by berman.michael-chastain.com (Postfix, from userid 502) id 4EEED4B104; Tue, 6 Jul 2004 16:03:42 -0400 (EDT) To: cagney@gnu.org, mec.gnu@mindspring.com Subject: Re: gdb 6.2 blockers Cc: gdb@sources.redhat.com Message-Id: <20040706200342.4EEED4B104@berman.michael-chastain.com> Date: Tue, 06 Jul 2004 20:03:00 -0000 From: mec.gnu@mindspring.com (Michael Elizabeth Chastain) X-SW-Source: 2004-07/txt/msg00049.txt.bz2 ac> BTW, I did try to reproduce this bug. Mainline GDB and manythreads.exp ac> appear to work everytime on NPTL based FC2 and RHEL2 GNU/Linux systems ac> (well at least for the 30+ test runs I tried). That wasn't the case ac> with 6.1. Cool. Could you cc: gdb-gnats on that? I'm trying to use gnats to collect history for complicated bugs like this. I'm adding an RHEL3 machine soon. hp test drive has an eight processor machine running RHEL3! ac> We should probably mention this fix in the NEWS file, and the apparent ac> linuxthreads regression in PROBLEMS. If the PR is listed in PROBLEMS then it's totally okay with me. (In my dream world, a user sees the PR number in PROBLEMS, reads the PR to acquire all the information that we've discovered, and becomes motivated to fix the problem and join the gdb developer community). Michael C