If one sets a BPINT 3, the current debugger will not actually break on INT 3 instructions. The following patch fixes that. It is useful for debugging code which utilizes INT 3.
Note that this is for INT3 via opcode (0xcc). INT3 via opcodes (0xcd 0x03) already works.
I am slightly confused as to why we should break on breakpoints that we don;t set ? Wouldn't this be triggering all kinds of anti-debugger tricks ?
Log in to post a comment.
Note that this is for INT3 via opcode (0xcc). INT3 via opcodes (0xcd 0x03) already works.
I am slightly confused as to why we should break on breakpoints that we don;t set ?
Wouldn't this be triggering all kinds of anti-debugger tricks ?