From: Jim Blandy <jimb@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: [obvious]: More "Linux" -> "GNU/Linux"
Date: Wed, 25 Jun 2003 00:53:00 -0000 [thread overview]
Message-ID: <vt23chzcbro.fsf@zenia.home> (raw)
2003-06-24 Jim Blandy <jimb@redhat.com>
* ppc-linux-tdep.c: More "Linux" -> "GNU/Linux".
*** gdb/ppc-linux-tdep.c.~1.36.~ 2003-06-24 18:06:07.000000000 -0500
--- gdb/ppc-linux-tdep.c 2003-06-24 18:09:02.000000000 -0500
***************
*** 731,737 ****
}
! /* If DESC is the address of a 64-bit PowerPC Linux function
descriptor, return the descriptor's entry point. */
static CORE_ADDR
ppc64_desc_entry_point (CORE_ADDR desc)
--- 731,737 ----
}
! /* If DESC is the address of a 64-bit PowerPC GNU/Linux function
descriptor, return the descriptor's entry point. */
static CORE_ADDR
ppc64_desc_entry_point (CORE_ADDR desc)
***************
*** 894,915 ****
}
! /* Support for CONVERT_FROM_FUNC_PTR_ADDR(ADDR) on PPC64 Linux.
Usually a function pointer's representation is simply the address
! of the function. On Linux on the 64-bit PowerPC however, a function
! pointer is represented by a pointer to a TOC entry. This TOC entry
! contains three words, the first word is the address of the
! function, the second word is the TOC pointer (r2), and the third
! word is the static chain value. Throughout GDB it is currently
! assumed that a function pointer contains the address of the
! function, which is not easy to fix. In addition, the conversion of
! a function address to a function pointer would require allocation
! of a TOC entry in the inferior's memory space, with all its
! drawbacks. To be able to call C++ virtual methods in the inferior
! (which are called via function pointers), find_function_addr uses
! this function to get the function address from a function
! pointer. */
/* Return real function address if ADDR (a function pointer) is in the data
space and is therefore a special function pointer. */
--- 894,915 ----
}
! /* Support for CONVERT_FROM_FUNC_PTR_ADDR(ADDR) on PPC64 GNU/Linux.
Usually a function pointer's representation is simply the address
! of the function. On GNU/Linux on the 64-bit PowerPC however, a
! function pointer is represented by a pointer to a TOC entry. This
! TOC entry contains three words, the first word is the address of
! the function, the second word is the TOC pointer (r2), and the
! third word is the static chain value. Throughout GDB it is
! currently assumed that a function pointer contains the address of
! the function, which is not easy to fix. In addition, the
! conversion of a function address to a function pointer would
! require allocation of a TOC entry in the inferior's memory space,
! with all its drawbacks. To be able to call C++ virtual methods in
! the inferior (which are called via function pointers),
! find_function_addr uses this function to get the function address
! from a function pointer. */
/* Return real function address if ADDR (a function pointer) is in the data
space and is therefore a special function pointer. */
***************
*** 929,935 ****
}
! /* 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
--- 929,935 ----
}
! /* On 64-bit PowerPC GNU/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
***************
*** 1062,1068 ****
if (tdep->wordsize == 8)
{
! /* Handle PPC64 Linux function pointers (which are really
function descriptors). */
set_gdbarch_convert_from_func_ptr_addr
(gdbarch, ppc64_linux_convert_from_func_ptr_addr);
--- 1062,1068 ----
if (tdep->wordsize == 8)
{
! /* Handle PPC64 GNU/Linux function pointers (which are really
function descriptors). */
set_gdbarch_convert_from_func_ptr_addr
(gdbarch, ppc64_linux_convert_from_func_ptr_addr);
reply other threads:[~2003-06-25 0:53 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=vt23chzcbro.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