From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3713 invoked by alias); 11 Jun 2003 13:48:10 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 3344 invoked from network); 11 Jun 2003 13:48:05 -0000 Received: from unknown (HELO localhost.redhat.com) (207.219.125.131) by sources.redhat.com with SMTP; 11 Jun 2003 13:48:05 -0000 Received: from redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id A81412B63; Wed, 11 Jun 2003 09:48:03 -0400 (EDT) Message-ID: <3EE73313.6090207@redhat.com> Date: Wed, 11 Jun 2003 13:48:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.2) Gecko/20030223 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jim Blandy Cc: gdb-patches@sources.redhat.com Subject: Re: [ppc64-linux] gdbarch hook to find true execution entry point References: <3EE72E0F.4010607@redhat.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-06/txt/msg00368.txt.bz2 > 2003-06-11 Jim Blandy > > * gdbarch.sh (gdbarch_bfd_entry_point): New gdbarch method. > * arch-utils.c (generic_bfd_entry_point): New function. > * arch-utils.h (generic_bfd_entry_point): New declaration. > * gdbarch.c, gdbarch.h: Regenerated. > * solib-svr4.c (enable_break): Call it, instead of accessing > tmp_bfd->start_address directly. > I think this should be in BFD. Not just GDB but also the simulators are going to need this information. PS: If BFD does this, ENTRY_POINT_ADDRESS can also, finally, be deleted. Andrew