From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5937 invoked by alias); 5 May 2009 17:35:54 -0000 Received: (qmail 5923 invoked by uid 22791); 5 May 2009 17:35:53 -0000 X-SWARE-Spam-Status: No, hits=-2.1 required=5.0 tests=AWL,BAYES_00,J_CHICKENPOX_54 X-Spam-Check-By: sourceware.org Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 05 May 2009 17:35:48 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 84DFA2BAB2A for ; Tue, 5 May 2009 13:35:46 -0400 (EDT) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id CPgNO3VEgRy3 for ; Tue, 5 May 2009 13:35:46 -0400 (EDT) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 4569B2BAB99 for ; Tue, 5 May 2009 13:35:46 -0400 (EDT) Received: by joel.gnat.com (Postfix, from userid 1000) id 7F1A0F5900; Tue, 5 May 2009 10:35:40 -0700 (PDT) Date: Tue, 05 May 2009 17:35:00 -0000 From: Joel Brobecker To: gdb@sourceware.org Subject: update on the gdb-7.0 branch/release Message-ID: <20090505173540.GB894@adacore.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.18 (2008-05-17) Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2009-05/txt/msg00018.txt.bz2 Hello everyone, The targeted branch time (2009-05-08) is fast approaching, and there are still lots of items on the list. I think the following elements should be relatively quick&easy to fix: (1) Assert in frame.c:get_frame_arch. IIRC, this assert was added to control accesses to this function, but is not otherwise essential for correct behavior; So worse case scenario, we could simply remove the assert on the branch while we investigate a proper fix on the HEAD. (2) Python pretty-printing: 1 issue left: Printing strings with NUL characters in them. Is that blocking? Or can we fix quickly? (3) PR/9723: gdb breakpoints silently fail on PIE binaries We don't need to fix this issue, but we need to add a warning that PIE is not supported. On the other hand, the following might be tricky: (4) PR/9711: Quadratic slowdown for "where" command. This was deemed blocking for the release. Not sure about the following two items: (5) PR/9786: Typing "info frame" immediately after connecting to a remote target causes an assertion error on x86 GNU/Linux (32 bit). (6) Commands attached to breakpoints Apparently, an annoying bug. At this point, it seems too late to think about including inlining support in 7.0: (7) Inlining support: Has Mark removed his objection based on Daniel's answers to his latest remarks? One of the issues I should mention is my availability. Unfortunately, I don't think I'll be able to fulfill my duties until May 18. I'll also be away 10 days starting May 28, with only sporadic email access. Given all that, I'm not sure it's wise to try to push for a release before the summit. What I suggest is that we try to address all the issues above ASAP, and then branch as soon as we're satisfied. Or perhaps, we might still want to branch on time, and then address the issues on both head and branch. I'm OK with that. I'll delay the pre-release pending resolution of the issues if necessary. Thoughts? -- Joel