From: Kyle Huey <me@kylehuey.com>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Do arm_abi detection for ELFOSABI_GNU binaries
Date: Fri, 08 May 2015 17:12:00 -0000 [thread overview]
Message-ID: <CAP045ApZ9xcDwDk45CXcd=0gxhqsTcUcJ9jAER4RkRn1RCs_Vg@mail.gmail.com> (raw)
In-Reply-To: <86sibzrvtv.fsf@gmail.com>
On Fri, Apr 17, 2015 at 1:41 AM, Yao Qi <qiyaoltc@gmail.com> wrote:
> Kyle Huey <me@kylehuey.com> writes:
>
> Hi Kyle,
>
>> 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)
>
> Thanks for submitting the patch... Looks GDB doesn't detect the correct
> abi in your case, but you can set arm abi explicitly via "set arm abi AAPCS".
> Hope this can unblock you. In the mean time, I'll think about your patch.
>
> --
> Yao (齐尧)
Hello Yao,
Thank you for the tip. Have you had a chance to look at the patch?
- Kyle
next prev parent reply other threads:[~2015-05-08 17:12 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
2015-04-17 8:41 ` Yao Qi
2015-05-08 17:12 ` Kyle Huey [this message]
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='CAP045ApZ9xcDwDk45CXcd=0gxhqsTcUcJ9jAER4RkRn1RCs_Vg@mail.gmail.com' \
--to=me@kylehuey.com \
--cc=gdb-patches@sourceware.org \
--cc=qiyaoltc@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).