Backtrace on "Watch (Read &) Write Access" about bit-slicer

[zorgiepoo]

The target crashing is likely due to a defect in the debugger not being able to handle a breakpoint being hit simultaneously from different threads very well.. I'm seeing if I can improve this; the debugger code is more complex than I'd like :|.

Getting the stack trace is not easy currently. Generating the stack trace each time a watchpoint was hit is expensive and the code would need to shifted/refactored to do it once per unique address, but I don't think it's worth making that change. More reasonable is a feature request of halting in the debugger for the first watch access, maybe.

A neat workaround is injecting your own bit of code in the debugger. This will lead to much faster execution too. Eg:

cmp eax, 0x2
jne SKIP
nop ; <— SET BREAKPOINT HERE
SKIP:

[Sapd]

Thanks for your reply.
I imagined, that for every line in the Watch Window, you would get one backtrace (the first time it appeared).

I tried your injecting approach. But for some reason the target crashes after injecting:

I also tried it at another point which accessed the variable too, there it didn't crash but it also didn't trigger the breakpoint. Could it be because the address in cmp is wrong? I simply used the one the watch window shows "Watching 32-bit write accesses at ADDRESS".

[zorgiepoo]

Late response, but because the instruction is:
mov [esi], edi

I'd probably want to compare esi (the memory address) or edi (the new value)
eax is assigned afterwards.