From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31657 invoked by alias); 21 Jun 2004 13:30:27 -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 31643 invoked from network); 21 Jun 2004 13:30:27 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org with SMTP; 21 Jun 2004 13:30:27 -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 i5LDURe3008524 for ; Mon, 21 Jun 2004 09:30:27 -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 i5LDUQ020363; Mon, 21 Jun 2004 09:30:26 -0400 Received: from gnu.org (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 8DF442B9D; Mon, 21 Jun 2004 09:30:15 -0400 (EDT) Message-ID: <40D6E2E7.3020908@gnu.org> Date: Mon, 21 Jun 2004 13:30: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: Jim Blandy Cc: gdb@sources.redhat.com Subject: Re: Post GDB 6.2, require new frame code References: <40D34274.50803@gnu.org> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2004-06/txt/msg00207.txt.bz2 So you see no problems with the schedule? That, given the rapidly aproaching 6.2 branch, is the key question here. As for an informational message during startup, that's in line with an earlier proposal I put forward: alert the user of any reliance on deprecated mechanisms during startup. It was rejected as it was felt that it would unnecessarially scare (for want of a better word) the users. Here though, the message is for a very specific problem and clear outcome so will probably be considered ok. Andrew