Fix PR server/20414 - x32 gdbserver always crashes inferior
authorPedro Alves <palves@redhat.com>
Tue, 26 Jul 2016 21:21:27 +0000 (22:21 +0100)
committerPedro Alves <palves@redhat.com>
Tue, 26 Jul 2016 21:21:27 +0000 (22:21 +0100)
commit6598661d14c90cabac1daa5e683d1e17883b2e41
tree85dcaceff4c037cdf546a41b6ea54f2c256e7a3b
parent0b31a4bcec2efec9bc8ca40deb61123c52690a2e
Fix PR server/20414 - x32 gdbserver always crashes inferior

Debugging an x32 process with an x32 gdbserver always results in:

 (gdb) c
 Continuing.

 Program received signal SIGSEGV, Segmentation fault.
 0xf7de9600 in _dl_debug_state () from target:/libx32/ld-linux-x32.so.2
 (gdb)

Looking at the remote debug logs reveals the problem, here:

  Packet received: T05swbreak:;06:a0d4ffff00000000;07:b8d3ffff00000000;10:0096def701000000;thread:p7d7a.7d7a;core:1;
                                                                          ^^^^^^^^^^^^^^^^

The underlined value is the expedited value of RIP (in little endian).
But notice that 01 in 0x01f7de9600, while gdb says the program stopped
at 0xf7de9600.  0x01ffffffff is over 32 bits, which indicates that
something wen't wrong somewhere in gdbserver.

The problem turns out to be in gdbserver's x86_get_pc / x86_set_pc
routines, where "unsigned long" is used assuming that it can fit a
64-bit value, while unsigned long is actually 32-bit on x32.  The
result is that collect_register_by_name / supply_register_by_name end
up reading/writing random bytes off the stack.

Fix this by using explicit uint64_t instead of unsigned long.
For consistency, use uint32_t instead of unsigned int in the 32-bit
paths.

gdb/gdbserver/ChangeLog:
2016-07-26  Pedro Alves  <palves@redhat.com>

PR server/20414
* linux-x86-low.c (x86_get_pc, x86_set_pc): Use uint64_t instead
of unsigned long for 64-bit registers and use uint32_t instead of
unsigned int for 32-bit registers.
gdb/gdbserver/ChangeLog
gdb/gdbserver/linux-x86-low.c
This page took 0.026038 seconds and 4 git commands to generate.