Joshua J. Drake 29c2670039 Fix #4560: Handle recoils well with swstep=true ...

When resuming after (during) recoil from a breakpoint, the swstep
implementation would fail to advance. In short, the debugger would immediately
interrupt again because r_bp_restore was re-setting the original breakpoint
just before continue. The following changes fix this issue:

1. Modify r_bp_get_in to stop including the byte after a breakpoint. This was
causing r_bp_recoil to fail because it thought there was already a breakpoint
on the next instruction.

2. Pass the real breakpoint address (pc - dbg->bpsize) to r_bp_recoil so
that r_bp_get_in can work properly. Stop adding the b->size there to keep it
going too.

3. Add a state flag to core->dbg to track that we are in the midst of a recoil.

4. When continuing from recoil (in r_debug_continue_kill), restore all
breakpoints except the one we just hit (with the new r_bp_restore_except) to
avoid hitting it again. Once we move past this instruction, that breakpoint
will be set again.

2016-05-15 10:19:24 +02:00

..

p

Fix w32 debugger

2016-05-11 13:09:40 +02:00

t

…

arg.c

Fix syscall resolution after 0a4a2615c91d0fbdbf9fd2f777cc2ec7b38e8981

2016-04-22 19:33:23 +02:00

debug.c

Fix #4560: Handle recoils well with swstep=true

2016-05-15 10:19:24 +02:00

desc.c

…

esil.c

…

Jamroot

…

Makefile

…

map.c

…

pid.c

Fix #4673 - dpt sync with help msg

2016-04-21 15:21:56 +02:00

plugin.c

fix double free on register

2016-04-13 21:30:48 -04:00

reg.c

libr: fix compilation warnings

2016-05-13 09:57:55 +02:00

signal.c

…

snap.c

…

trace.c

…