From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11551 invoked by alias); 10 Jun 2011 14:17:53 -0000 Received: (qmail 11526 invoked by uid 22791); 10 Jun 2011 14:17:52 -0000 X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 tests=AWL,BAYES_00,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (38.113.113.100) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 10 Jun 2011 14:17:38 +0000 Received: (qmail 1197 invoked from network); 10 Jun 2011 14:17:37 -0000 Received: from unknown (HELO digraph.polyomino.org.uk) (joseph@127.0.0.2) by mail.codesourcery.com with ESMTPA; 10 Jun 2011 14:17:37 -0000 Received: from jsm28 (helo=localhost) by digraph.polyomino.org.uk with local-esmtp (Exim 4.72) (envelope-from ) id 1QV2Wl-0000zc-48; Fri, 10 Jun 2011 14:17:35 +0000 Date: Fri, 10 Jun 2011 14:17:00 -0000 From: "Joseph S. Myers" To: Jakub Jelinek cc: libc-alpha@sourceware.org, binutils@sourceware.org, gdb@sourceware.org, Mark Wielaard , Frank Eigler Subject: Re: RFC: Unwind info for PLT In-Reply-To: <20110610074524.GR17079@tyan-ft48-01.lab.bos.redhat.com> Message-ID: References: <20110610074524.GR17079@tyan-ft48-01.lab.bos.redhat.com> 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: 2011-06/txt/msg00071.txt.bz2 On Fri, 10 Jun 2011, Jakub Jelinek wrote: > Anyway, I think hardcoding this in the linker would be problematic, > we couldn't tweak it, so providing some special hidden symbols around > the .plt section and let glibc crtfiles provide it sounds like the best > option to me. I think that when the linker generates code it should generate unwind info for it to allow accurate backtraces from any instruction (both .eh_frame and .debug_frame, or target-specific forms on some targets). The details of this generated code may not be part of the ABI on all targets, may vary depending on the linker version and may be a lot more complicated than a single PLT section - there are lots of purposes for which the linker may generate code. I don't think glibc crtfiles are a good place for it. -- Joseph S. Myers joseph@codesourcery.com