From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28708 invoked by alias); 22 Aug 2006 21:04:23 -0000 Received: (qmail 28698 invoked by uid 22791); 22 Aug 2006 21:04:22 -0000 X-Spam-Check-By: sourceware.org Received: from sibelius.xs4all.nl (HELO sibelius.xs4all.nl) (82.92.89.47) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 22 Aug 2006 21:04:21 +0000 Received: from elgar.sibelius.xs4all.nl (root@elgar.sibelius.xs4all.nl [192.168.0.2]) by sibelius.xs4all.nl (8.13.4/8.13.4) with ESMTP id k7ML4DZZ016609; Tue, 22 Aug 2006 23:04:13 +0200 (CEST) Received: from elgar.sibelius.xs4all.nl (kettenis@localhost.sibelius.xs4all.nl [127.0.0.1]) by elgar.sibelius.xs4all.nl (8.13.6/8.13.6) with ESMTP id k7ML4DVe026557; Tue, 22 Aug 2006 23:04:13 +0200 (CEST) Received: (from kettenis@localhost) by elgar.sibelius.xs4all.nl (8.13.6/8.13.6/Submit) id k7ML4D0w031633; Tue, 22 Aug 2006 23:04:13 +0200 (CEST) Date: Tue, 22 Aug 2006 21:31:00 -0000 Message-Id: <200608222104.k7ML4D0w031633@elgar.sibelius.xs4all.nl> From: Mark Kettenis To: brobecker@adacore.com CC: gdb-patches@sourceware.org In-reply-to: <20060822204119.GC1060@adacore.com> (message from Joel Brobecker on Tue, 22 Aug 2006 13:41:19 -0700) Subject: Re: [commit] Fix flags type initialization bug References: <200608221945.k7MJjJCr013229@elgar.sibelius.xs4all.nl> <20060822204119.GC1060@adacore.com> 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/msg00173.txt.bz2 > Date: Tue, 22 Aug 2006 13:41:19 -0700 > From: Joel Brobecker > > > I'm working on printing proper flags for some registers on SPARC when > > I hit this. It makes gdb crash, so perhaps I should put this on the > > release branch too? > > 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. > 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. Mark