Setting Breakpoints & Stepping Instructions
Set breakpoint, Step-over, and Step-in
In HyperDbg, we have multiple options to set a breakpoint.
One of the ways of setting breakpoints is hooking. Another way is using the 'bp' command. In this article, we describe the second method.
Assume that ObRegisterCallbacks is located at fffff805`5cbac610.
This function creates callbacks for thread, process, and other objects' tasks like creation, opening, etc. You can see more information at MSDN.
Many game anti-cheat solutions use this function to monitor processes to prevent game cheater to cheat on games.
In order to bypass this mechanism, we use the following command in HyperDbg to set a breakpoint on this function.
1
0: kHyperDbg> bp nt!ObRegisterCallbacks
Copied!
or,
1
0: kHyperDbg> bp fffff805`5cbac610
Copied!
Then, we will run our game and see if the breakpoint is triggered or not.
If the breakpoint is triggered, then the system is halt and we are able to control the debuggee.
After that, we can use the 'p' command to step-over the instructions.
1
0: kHyperDbg> p
2
fffff805`5cbac610 48 81 EC 50 01 00 00 sub rsp, 0x150
Copied!
You can also add a number to run multiple instructions.
1
0: kHyperDbg> p 3
2
fffff805`5cbac610 48 81 EC 50 01 00 00 sub rsp, 0x150
3
fffff805`5cbac617 48 8D AC 24 80 00 00 00 lea rbp, ss:[rsp+0x80]
4
fffff805`5cbac620 C6 45 AB 00 mov byte ptr ss:[rbp-0x55], 0x00
Copied!
If you want to step-in, you can use the 't' command.
1
0: kHyperDbg> t
2
fffff805`5cbac610 48 81 EC 50 01 00 00 sub rsp, 0x150
Copied!
Copy link
Edit on GitHub