From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18232 invoked by alias); 6 Jul 2004 18:24:19 -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 18178 invoked from network); 6 Jul 2004 18:24:18 -0000 Received: from unknown (HELO barry.mail.mindspring.net) (207.69.200.25) by sourceware.org with SMTP; 6 Jul 2004 18:24:18 -0000 Received: from user-119a90a.biz.mindspring.com ([66.149.36.10] helo=berman.michael-chastain.com) by barry.mail.mindspring.net with esmtp (Exim 3.33 #1) id 1Bhuc5-0005Wn-00; Tue, 06 Jul 2004 14:24:17 -0400 Received: by berman.michael-chastain.com (Postfix, from userid 502) id 393F34B104; Tue, 6 Jul 2004 14:24:23 -0400 (EDT) To: cagney@gnu.org, gdb@sources.redhat.com Subject: Re: gdb 6.2 blockers Message-Id: <20040706182423.393F34B104@berman.michael-chastain.com> Date: Tue, 06 Jul 2004 18:24:00 -0000 From: mec.gnu@mindspring.com (Michael Elizabeth Chastain) X-SW-Source: 2004-07/txt/msg00046.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. ac> - architecture specific problems HP/UX, and much of e500, that can be ac> committed after the branch 1692 is not arch-specific. The bug was introduced by a change in bp_stop_status, and partially fixed by a change in bp_stop_status. gdb recognizes its watchpoints now, but cannot backtrace after hitting one. The 32-vs-64-bit register change is definitely arch-specific. All the changes are available at: http://www.shout.net/~mec/sunday/2004-07-02-hpux/difference/6.1-HEAD-0.html I don't accept your conclusion that changes which manifest on hpux must be in arch-specific code. I won't know until I dig into each of the 14 test scripts with regressed results. It's up to me to do that and file PR's. Michael C