From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17171 invoked by alias); 6 Jul 2004 17:07:04 -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 17144 invoked from network); 6 Jul 2004 17:07:03 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org with SMTP; 6 Jul 2004 17:07:03 -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 i66H73e3010632 for ; Tue, 6 Jul 2004 13:07:03 -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 i66H72013749; Tue, 6 Jul 2004 13:07:03 -0400 Received: from gnu.org (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 5BEB82B9D; Tue, 6 Jul 2004 13:06:51 -0400 (EDT) Message-ID: <40EADC2B.7080504@gnu.org> Date: Tue, 06 Jul 2004 17:07: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: gdb@sources.redhat.com Subject: gdb 6.2 blockers Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2004-07/txt/msg00043.txt.bz2 Hello, The first thing to do is look over what's already been fixed, and why we should push out a new release: - signal trampolines ``work'' (ignoring kernel bugs :-) - dwarf 2 cygwin support - lots of new (or revised) native configurations - this kvm thingie whats it (mark needs a news entry) - the `start' command - ppc64 is ``so much better'' - what else? however, onto the issue. Here's a list of what I know of that could potentially block 6.2: 1650: I suspect this is really a kernel race condition. I remember that Jeff was pointing out that the bug this tickles is a race condition (hence isn't always reproducable). The fix for NPTL involves kernel changes, I'm not sure about linuxthreads. HP/UX: ``regressions'' This needs to be balanced against all the additional tests that do now pass. Some bits are working much better than ever before, just not all :-) vsyscall: For those following BFD you'll see I'm having fun closing this :-) PIE: This stuff needs to be reviewed/merged. inter-cu: This stuff needs to be reviewed/merged. e500: Architecture problems. Also dw_op_piece, xregset, ... I think we can split this into three problems: - 1650 is an issue, but even there I'm wondering how much. It's ticking a horrible nasty race condition and may not be a real problem in the field - do people really run 100 thread programs using linuxthreads. - architecture specific problems HP/UX, and much of e500, that can be committed after the branch - new features - inter-cu, PIE, VSYSCALL, inter-cu, xregset? dw_op_piece These should all go into the mainline. In some cases, these have been missing for years. Andrew