From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22621 invoked by alias); 23 Aug 2006 05:11:29 -0000 Received: (qmail 22604 invoked by uid 22791); 23 Aug 2006 05:11:27 -0000 X-Spam-Check-By: sourceware.org Received: from nile.gnat.com (HELO nile.gnat.com) (205.232.38.5) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 23 Aug 2006 05:11:25 +0000 Received: from localhost (localhost [127.0.0.1]) by filtered-nile.gnat.com (Postfix) with ESMTP id 95BC148CD9C; Wed, 23 Aug 2006 01:11:23 -0400 (EDT) Received: from nile.gnat.com ([127.0.0.1]) by localhost (nile.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 07125-02-2; Wed, 23 Aug 2006 01:11:23 -0400 (EDT) Received: from takamaka.act-europe.fr (unknown [70.71.0.212]) by nile.gnat.com (Postfix) with ESMTP id 4D32F48CBE6; Wed, 23 Aug 2006 01:11:23 -0400 (EDT) Received: by takamaka.act-europe.fr (Postfix, from userid 507) id 93ED547EFA; Tue, 22 Aug 2006 22:11:22 -0700 (PDT) Date: Wed, 23 Aug 2006 17:38:00 -0000 From: Joel Brobecker To: Mark Kettenis Cc: gdb-patches@sourceware.org Subject: Re: [commit] Fix flags type initialization bug Message-ID: <20060823051122.GD1060@adacore.com> References: <200608221945.k7MJjJCr013229@elgar.sibelius.xs4all.nl> <20060822204119.GC1060@adacore.com> <200608222104.k7ML4D0w031633@elgar.sibelius.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200608222104.k7ML4D0w031633@elgar.sibelius.xs4all.nl> User-Agent: Mutt/1.4i Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2006-08/txt/msg00179.txt.bz2 > > Is there a way to cause GDB 6.5 to crash, or is only after you > > applied your changes? > > This is used in i386-tdep.c since january or so, and I think there is > a risk of having it crash there, but I've never seen it happen. If there is a risk, then let's apply the patch. Let me know if you'd like me to do it. I have a check out of the branch already available, so I can do it pretty efficiently. > > Right now, I don't have any plan in making a minor release from > > the 6.5 branch, but I don't mind making one if the fixes of this > > kind keep piling up. > > This one alone isn't enough, but if there are a few others like it > that can potentially crash gdb itself, I think we should consider > having a 6.5.1 release. You're no3 on the list of fixes that made it to the branch. I try to be careful in my review of the patches that are applied, so hopefully I didn't miss any. My idea was to make a 6.5.1 release in october or november if I had enough patches. 3 could qualify as enough. Maybe we'll have a couple more by then. -- Joel