From: Jim Blandy <jimb@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: [gdb_6_0-branch commit] PPC64: new call_dummy_address gdbarch method
Date: Sat, 28 Jun 2003 00:23:00 -0000 [thread overview]
Message-ID: <vt2llvnaw5n.fsf@zenia.home> (raw)
I've committed this to the 6.0 branch, with verbal approval on the
phone from Kevin Buettner, the PPC Linux maintainer. It is already
committed to the trunk.
2003-06-06 Jim Blandy <jimb@redhat.com>
* ppc-linux-tdep.c (ppc64_call_dummy_address): New function.
(ppc_linux_init_abi): Set it as the gdbarch's call_dummy_address
method.
Index: gdb/ppc-linux-tdep.c
===================================================================
RCS file: /cvs/src/src/gdb/ppc-linux-tdep.c,v
retrieving revision 1.28.8.5
diff -c -r1.28.8.5 ppc-linux-tdep.c
*** gdb/ppc-linux-tdep.c 7 Jun 2003 00:06:05 -0000 1.28.8.5
--- gdb/ppc-linux-tdep.c 7 Jun 2003 00:15:33 -0000
***************
*** 893,898 ****
--- 893,910 ----
}
+ /* On 64-bit PowerPC Linux, the ELF header's e_entry field is the
+ address of a function descriptor for the entry point function, not
+ the actual entry point itself. So to find the actual address at
+ which execution should begin, we need to fetch the function's entry
+ point from that descriptor. */
+ static CORE_ADDR
+ ppc64_call_dummy_address (void)
+ {
+ return ppc64_desc_entry_point (entry_point_address ());
+ }
+
+
enum {
ELF_NGREG = 48,
ELF_NFPREG = 33,
***************
*** 1014,1019 ****
--- 1026,1033 ----
if (tdep->wordsize == 8)
{
+ set_gdbarch_call_dummy_address (gdbarch, ppc64_call_dummy_address);
+
set_gdbarch_in_solib_call_trampoline
(gdbarch, ppc64_in_solib_call_trampoline);
set_gdbarch_skip_trampoline_code (gdbarch, ppc64_skip_trampoline_code);
reply other threads:[~2003-06-28 0:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=vt2llvnaw5n.fsf@zenia.home \
--to=jimb@redhat.com \
--cc=gdb-patches@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox