This is the mail archive of the gdb-patches@sources.redhat.com mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [ppc64-linux] gdbarch hook to find true execution entry point

From: Andrew Cagney <ac131313 at redhat dot com>
To: Jim Blandy <jimb at redhat dot com>
Cc: gdb-patches at sources dot redhat dot com
Date: Wed, 11 Jun 2003 09:48:03 -0400
Subject: Re: [ppc64-linux] gdbarch hook to find true execution entry point
References: <vt24r2wu4ty.fsf@zenia.home> <3EE72E0F.4010607@redhat.com>

2003-06-11 Jim Blandy <jimb@redhat.com>

    * 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

References:
- [ppc64-linux] gdbarch hook to find true execution entry point
  - From: Jim Blandy
- Re: [ppc64-linux] gdbarch hook to find true execution entry point
  - From: Andrew Cagney

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]