From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5257 invoked by alias); 2 Sep 2009 15:22:48 -0000 Received: (qmail 5249 invoked by uid 22791); 2 Sep 2009 15:22:47 -0000 X-SWARE-Spam-Status: No, hits=-2.4 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 02 Sep 2009 15:22:37 +0000 Received: from int-mx02.intmail.prod.int.phx2.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id n82FMVpM025142; Wed, 2 Sep 2009 11:22:32 -0400 Received: from ns3.rdu.redhat.com (ns3.rdu.redhat.com [10.11.255.199]) by int-mx02.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id n82FMVdb027823; Wed, 2 Sep 2009 11:22:31 -0400 Received: from opsy.redhat.com (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by ns3.rdu.redhat.com (8.13.8/8.13.8) with ESMTP id n82FMTQ1011009; Wed, 2 Sep 2009 11:22:30 -0400 Received: by opsy.redhat.com (Postfix, from userid 500) id 6F699378242; Wed, 2 Sep 2009 09:22:29 -0600 (MDT) From: Tom Tromey To: Mark Kettenis Cc: teawater@gmail.com, gdb@sourceware.org Subject: Re: Does gdb can handle longjmp in i386 and amd64 now? References: <200909021516.n82FGlTf017321@brahms.sibelius.xs4all.nl> Reply-To: tromey@redhat.com Date: Wed, 02 Sep 2009 15:22:00 -0000 In-Reply-To: <200909021516.n82FGlTf017321@brahms.sibelius.xs4all.nl> (Mark Kettenis's message of "Wed, 2 Sep 2009 17:16:47 +0200 (CEST)") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2009-09/txt/msg00020.txt.bz2 >>>>> "Mark" == Mark Kettenis writes: Mark> I think it was the fact that it requires GDB to dig into glibc Mark> internals in combination with Ulrich Drepper no wanting to commit Mark> keeping those internals consistent. Oh, yeah, I forgot about the randomness and confused the current situation with a bug report I sent about gdb not working even with the LD_POINTER_GUARD=0 case: http://sourceware.org/bugzilla/show_bug.cgi?id=9832 In that case I think we can safely teach gdb about the mangling. In other cases, I don't know what to do. Continue to lose, I guess. Tom