aboutsummaryrefslogtreecommitdiff
path: root/gdb/python/py-event.c
diff options
context:
space:
mode:
authorKyle Huey <me@kylehuey.com>2015-05-28 09:12:12 +0100
committerYao Qi <yao.qi@linaro.org>2015-05-28 09:15:35 +0100
commitd403db2720ef6ac091dd1c0101ffc60242199528 (patch)
tree19dd36cbb3d4ec22365ef3d70f23c5ebdec00e28 /gdb/python/py-event.c
parent124b4f8708f534e44787d7edf22d214d2ec225be (diff)
downloadgdb-d403db2720ef6ac091dd1c0101ffc60242199528.zip
gdb-d403db2720ef6ac091dd1c0101ffc60242199528.tar.gz
gdb-d403db2720ef6ac091dd1c0101ffc60242199528.tar.bz2
Do arm_abi detection for ELFOSABI_GNU binaries
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/ 2015-05-28 Kyle Huey <me@kylehuey.com> (tiny patch) * gdb/arm-tdep.c (arm_gdbarch_init): Perform arm_abi detection on ELFOSABI_GNU binaries.
Diffstat (limited to 'gdb/python/py-event.c')
0 files changed, 0 insertions, 0 deletions