From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17263 invoked by alias); 6 Jan 2012 20:27:03 -0000 Received: (qmail 17217 invoked by uid 22791); 6 Jan 2012 20:27:02 -0000 X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,RCVD_IN_DNSWL_NONE X-Spam-Check-By: sourceware.org Received: from caibbdcaaaaf.dreamhost.com (HELO homiemail-a41.g.dreamhost.com) (208.113.200.5) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 06 Jan 2012 20:26:44 +0000 Received: from homiemail-a41.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a41.g.dreamhost.com (Postfix) with ESMTP id 6769E44C061; Fri, 6 Jan 2012 12:26:43 -0800 (PST) Received: from redwood.eagercon.com (c-76-102-3-160.hsd1.ca.comcast.net [76.102.3.160]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: eager@eagerm.com) by homiemail-a41.g.dreamhost.com (Postfix) with ESMTPSA id 08FBC44C058; Fri, 6 Jan 2012 12:26:43 -0800 (PST) Message-ID: <4F075902.1020500@eagerm.com> Date: Fri, 06 Jan 2012 20:27:00 -0000 From: Michael Eager User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:8.0) Gecko/20111115 Thunderbird/8.0 MIME-Version: 1.0 To: "Joseph S. Myers" CC: gdb@sourceware.org, Alan Modra Subject: Re: PowerPC SecurePLT - stepping into library function References: <4F075159.5090508@eagerm.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes 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: 2012-01/txt/msg00023.txt.bz2 On 01/06/2012 12:09 PM, Joseph S. Myers wrote: > On Fri, 6 Jan 2012, Michael Eager wrote: > >> It seems that the best way to fix this would be to create >> a new OSABI sniffer for SecurePLT which identifies that >> the executable was compiled with -msecurePLT. One issue >> is how to identify these programs. The Power Arch 32-bit ABI >> (Sect 5.2.5.2, note at end) says that these will have >> R_PPC_REL16 relocations. I don't see any of these relocs. > > That's about relocatable objects, i.e. static relocations in .o files, not > dynamic relocations in executables and shared libraries. I didn't see any in the .o files, either. >> Is there any possibility of a chimera: an executable compiled >> using Secure PLT linking to libraries which use the old style >> PLT? Or vice-versa? I'm assuming that this cannot happen. > > As far as I know that ought to work. Yeah, that's what I was afraid of. That means that an OSABI sniffer will not work. -- Michael Eager eager@eagercon.com 1960 Park Blvd., Palo Alto, CA 94306 650-325-8077