Remove non-address bits for longjmp resume breakpoint
authorAndreas Arnez <arnez@linux.vnet.ibm.com>
Thu, 9 Oct 2014 11:32:22 +0000 (11:32 +0000)
committerUlrich Weigand <ulrich.weigand@de.ibm.com>
Wed, 15 Oct 2014 15:32:38 +0000 (17:32 +0200)
commit8fa0c4f8ed9e520c39132bc62d51a490a17c537f
treefde84582439d703515edcd607e1302c5abfb45a6
parent3666da817e330c563c261cbe9086f4825f74de42
Remove non-address bits for longjmp resume breakpoint

On 32-bit S390 targets the longjmp target address "naturally" has the
most significant bit set.  That bit indicates the addressing mode and
is not part of the address itself.  Thus, in analogy with similar
cases (like when computing the caller PC in
insert_step_resume_breakpoint_at_caller), this change removes
non-address bits from the longjmp target address before using it as a
breakpoint address.

Note that there are two ways for determining the longjmp target
address: via a probe or via a gdbarch method.  This change only
affects the probe method, because it is assumed that the address
returned by the gdbarch method is usable as-is.

This change was tested together with a patch that enables longjmp
probes in glibc for S/390:

  https://sourceware.org/ml/libc-alpha/2014-10/msg00277.html

gdb/ChangeLog:

* gdb/infrun.c (process_event_stop_test): Apply
gdbarch_addr_bits_remove to longjmp resume address.
gdb/ChangeLog
gdb/infrun.c
This page took 0.023803 seconds and 4 git commands to generate.