From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27358 invoked by alias); 9 Nov 2012 16:54:00 -0000 Received: (qmail 27344 invoked by uid 22791); 9 Nov 2012 16:53:59 -0000 X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=AWL,BAYES_00,RCVD_IN_HOSTKARMA_NO 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; Fri, 09 Nov 2012 16:53:51 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 6FC7F1C7314; Fri, 9 Nov 2012 11:53:50 -0500 (EST) 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 jsRC+3Dss4NL; Fri, 9 Nov 2012 11:53:50 -0500 (EST) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 25DBC1C6C71; Fri, 9 Nov 2012 11:53:50 -0500 (EST) Received: by joel.gnat.com (Postfix, from userid 1000) id 49C11CA5BE; Fri, 9 Nov 2012 08:53:39 -0800 (PST) Date: Fri, 09 Nov 2012 16:54:00 -0000 From: Joel Brobecker To: Mark Kettenis Cc: palves@redhat.com, hjl.tools@gmail.com, gdb-patches@sourceware.org Subject: Re: [7.5] PATCH: PR backtrace/14646 [x32] backtrace doesn't work Message-ID: <20121109165339.GP5103@adacore.com> References: <20121020234741.GA3626@gmail.com> <20121021015636.GD3050@adacore.com> <509C4B2D.9090809@redhat.com> <201211090958.qA99wlke004638@glazunov.sibelius.xs4all.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201211090958.qA99wlke004638@glazunov.sibelius.xs4all.nl> User-Agent: Mutt/1.5.21 (2010-09-15) Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2012-11/txt/msg00249.txt.bz2 > > only had effect on x32. > > Yeah, it's pretty safe. Must say that I don't see the urgency as x32 > is still in its infancy. Thanks, guys. This takes care of my concerns regarding this patch. -- Joel