From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21934 invoked by alias); 18 Aug 2003 17:16:06 -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 21912 invoked from network); 18 Aug 2003 17:16:03 -0000 Received: from unknown (HELO concert.shout.net) (204.253.184.25) by sources.redhat.com with SMTP; 18 Aug 2003 17:16:03 -0000 Received: from duracef.shout.net (duracef.shout.net [204.253.184.12]) by concert.shout.net (8.12.9/8.12.9) with ESMTP id h7IHG2Ws005516; Mon, 18 Aug 2003 12:16:02 -0500 Received: from duracef.shout.net (localhost [127.0.0.1]) by duracef.shout.net (8.12.9/8.12.9) with ESMTP id h7IHG2HK003492; Mon, 18 Aug 2003 12:16:02 -0500 Received: (from mec@localhost) by duracef.shout.net (8.12.9/8.12.9/Submit) id h7IHG1IY003490; Mon, 18 Aug 2003 13:16:01 -0400 Date: Mon, 18 Aug 2003 17:16:00 -0000 From: Michael Elizabeth Chastain Message-Id: <200308181716.h7IHG1IY003490@duracef.shout.net> To: ac131313@redhat.com, gdb@sources.redhat.com Subject: Re: 6.0 issues X-SW-Source: 2003-08/txt/msg00200.txt.bz2 Andrew C says: - the gdb.cp re-vamp scheduled for near the end of this week Okay, you and david c both want to do this in the branch, so I will prepare to do it in the branch. But I might not make it in time. First I am waiting a few more days for comment, then I do it in HEAD, then I wait some more time to see if problems come up. It's fine with me if this misses the release -- I assume it's okay with you? > New features shouldn't be going into the 6.0 branch (although there is > an extreem tollerance towards targets getting their frame code rewritten > :-). In this category I would like to add: Mark K's fix for gdb/1338, "can't backtrace through select". Michael C