From: Kyle Huey <me@kylehuey.com>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH] Do arm_abi detection for ELFOSABI_GNU binaries
Date: Thu, 16 Apr 2015 17:15:00 -0000 [thread overview]
Message-ID: <CAP045ApteDb3EVgF2fsxWcjmsS48DSBKuYo1Yc7QR2C29f8iRQ@mail.gmail.com> (raw)
In-Reply-To: <CAP045ApGo8tPc=97OqrVG4S9GiAP+T1k0ftrP2L3f-kpCDSdJg@mail.gmail.com>
On Fri, Mar 27, 2015 at 1:55 PM, Kyle Huey <me@kylehuey.com> wrote:
> On ARM systems, gdb must determine which style of breakpoint to use
> (see the comments at the beginning of gdb/arm-linux-tdep.c). In
> arm_gdbarch_init we only attempt to extract the eabi version from the
> ELF binary if it is a ELFOSABI_NONE binary. If the binary is
> ELFOSABI_GNU instead, we end up defaulting to the old style OABI
> syscall breakpoint instruction. On a Linux kernel built without
> CONFIG_OABI_COMPAT, this triggers a SIGILL in ld when attempting to
> execute any ELFOSABI_GNU program. (e.g.
> https://github.com/raspberrypi/linux/issues/766)
>
> gdb/ChangeLog:
> * gdb/arm-tdep.c (arm_gdbarch_init): Perform arm_abi detection on
> ELFOSABI_GNU binaries.
> ---
> gdb/arm-tdep.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/gdb/arm-tdep.c b/gdb/arm-tdep.c
> index 630a207..830739e 100644
> --- a/gdb/arm-tdep.c
> +++ b/gdb/arm-tdep.c
> @@ -9948,17 +9948,17 @@ arm_gdbarch_init (struct gdbarch_info info,
> struct gdbarch_list *arches)
>
> if (ei_osabi == ELFOSABI_ARM)
> {
> /* GNU tools used to use this value, but do not for EABI
> objects. There's nowhere to tag an EABI version
> anyway, so assume APCS. */
> arm_abi = ARM_ABI_APCS;
> }
> - else if (ei_osabi == ELFOSABI_NONE)
> + else if (ei_osabi == ELFOSABI_NONE || ei_osabi == ELFOSABI_GNU)
> {
> int eabi_ver = EF_ARM_EABI_VERSION (e_flags);
> int attr_arch, attr_profile;
>
> switch (eabi_ver)
> {
> case EF_ARM_EABI_UNKNOWN:
> /* Assume GNU tools. */
Bump. Has anyone had a chance to review this?
- Kyle
next prev parent reply other threads:[~2015-04-16 17:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-27 20:55 Kyle Huey
2015-04-16 17:15 ` Kyle Huey [this message]
2015-04-17 8:41 ` Yao Qi
2015-05-08 17:12 ` Kyle Huey
2015-05-19 9:41 ` Yao Qi
2015-05-19 14:04 ` Kyle Huey
2015-05-28 8:19 ` Yao Qi
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=CAP045ApteDb3EVgF2fsxWcjmsS48DSBKuYo1Yc7QR2C29f8iRQ@mail.gmail.com \
--to=me@kylehuey.com \
--cc=gdb-patches@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).