You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This doesn't work because we implement the rsi by setting a breakpoint in the code region and replaying forward to the breakpoint. But the breakpoint is overwritten by the code copy, so that doesn't work.
We can avoid it by using a hardware breakpoint, but that would steal a hardware breakpoint from users, which would be worse in general. This bug hardly ever comes up.
FWIW this isn't a problem in Pernosco which takes a totally different approach to debugging replay.
Maybe we could add an option to always use a hardware breakpoint for replay, and suggest using it if we crash in this way. This would be pretty easy on top of PR #3731.
i have the following nasm which loads a part of itself into a region in memory and executes from there .
replaying it backwards with rr crashes when it enters the mmaped region.
nasm code
test.nasm
:compile and link
record program with rr,
replay program to the end
step backwards by instruction (
rsi
) till it execution reaches from mmap region.rr crashes with a message like
The text was updated successfully, but these errors were encountered: