Difference between revisions of "Duby/Breakpoint"
m |
m |
||
| Line 2: | Line 2: | ||
===Code Modification=== | ===Code Modification=== | ||
| − | In the force case scenario, breakpoints are set by changing the code and setting debugging code (for x86). | + | In the force case scenario, breakpoints are set by changing the existing code and setting debugging code (for x86) interruption. |
| + | |||
| + | The code has a length of 1 byte, thus it's safe to modify an existing instruction (of any length). | ||
| + | |||
| + | However, it's necessary to know, where an instruction actually begins. (Without debugging information, the only way to know where an instruction begins is through careful disassembling) | ||
==See Also== | ==See Also== | ||
Revision as of 21:37, 27 October 2017
Setting Breakpoint
Code Modification
In the force case scenario, breakpoints are set by changing the existing code and setting debugging code (for x86) interruption.
The code has a length of 1 byte, thus it's safe to modify an existing instruction (of any length).
However, it's necessary to know, where an instruction actually begins. (Without debugging information, the only way to know where an instruction begins is through careful disassembling)
