Adjust breakpoint address by clearing non-significant bits
Tag in tagged address on AArch64 is treated as a non-significant bits of address, which can be got by gdbarch method significant_addr_bit, and gdb can clear these bits. With this patch, when user sets a breakpoint on tagged address on AArch64, GDB will drop the top byte of address, and put breakpoint at the new place, as shown below, (gdb) hbreak *func_ptr warning: Breakpoint address adjusted from 0xf000000000400690 to 0x00400690. Hardware assisted breakpoint 2 at 0x400690 (gdb) break *func_ptr warning: Breakpoint address adjusted from 0xf000000000400690 to 0x00400690. Breakpoint 3 at 0x400690 When program hits a breakpoint, the stopped pc reported by Linux kernel is the address *without* tag, so it is better the address recorded in breakpoint location is the one without tag too, so we can still match breakpoint location address and stopped pc reported by Linux kernel, by simple compare. gdb: 2017-12-08 Yao Qi <yao.qi@linaro.org> * breakpoint.c (adjust_breakpoint_address): Call address_significant. gdb/testsuite: 2017-12-08 Yao Qi <yao.qi@linaro.org> * gdb.arch/aarch64-tagged-pointer.c (main): Update. * gdb.arch/aarch64-tagged-pointer.exp: Add test for breakpoint.
This commit is contained in:
parent
a738ea1d41
commit
a0de8c21ba
5 changed files with 56 additions and 14 deletions
|
@ -6973,16 +6973,11 @@ static CORE_ADDR
|
|||
adjust_breakpoint_address (struct gdbarch *gdbarch,
|
||||
CORE_ADDR bpaddr, enum bptype bptype)
|
||||
{
|
||||
if (!gdbarch_adjust_breakpoint_address_p (gdbarch))
|
||||
{
|
||||
/* Very few targets need any kind of breakpoint adjustment. */
|
||||
return bpaddr;
|
||||
}
|
||||
else if (bptype == bp_watchpoint
|
||||
|| bptype == bp_hardware_watchpoint
|
||||
|| bptype == bp_read_watchpoint
|
||||
|| bptype == bp_access_watchpoint
|
||||
|| bptype == bp_catchpoint)
|
||||
if (bptype == bp_watchpoint
|
||||
|| bptype == bp_hardware_watchpoint
|
||||
|| bptype == bp_read_watchpoint
|
||||
|| bptype == bp_access_watchpoint
|
||||
|| bptype == bp_catchpoint)
|
||||
{
|
||||
/* Watchpoints and the various bp_catch_* eventpoints should not
|
||||
have their addresses modified. */
|
||||
|
@ -7000,11 +6995,16 @@ adjust_breakpoint_address (struct gdbarch *gdbarch,
|
|||
}
|
||||
else
|
||||
{
|
||||
CORE_ADDR adjusted_bpaddr;
|
||||
CORE_ADDR adjusted_bpaddr = bpaddr;
|
||||
|
||||
/* Some targets have architectural constraints on the placement
|
||||
of breakpoint instructions. Obtain the adjusted address. */
|
||||
adjusted_bpaddr = gdbarch_adjust_breakpoint_address (gdbarch, bpaddr);
|
||||
if (gdbarch_adjust_breakpoint_address_p (gdbarch))
|
||||
{
|
||||
/* Some targets have architectural constraints on the placement
|
||||
of breakpoint instructions. Obtain the adjusted address. */
|
||||
adjusted_bpaddr = gdbarch_adjust_breakpoint_address (gdbarch, bpaddr);
|
||||
}
|
||||
|
||||
adjusted_bpaddr = address_significant (gdbarch, adjusted_bpaddr);
|
||||
|
||||
/* An adjusted breakpoint address can significantly alter
|
||||
a user's expectations. Print a warning if an adjustment
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue