HyperDbg v0.16 is released!
If you’re enjoying HyperDbg, don’t forget to give a star 🌟 on GitHub!
Please visit Build & Install to configure the environment for running HyperDbg. Check out the Quick Start and Frequently Asked Questions (FAQs) to learn more. You can use the examples of using the debugger and the script engine to get started with HyperDbg.
Added
- The !xsetbv event command was added for handling the execution of the XSETBV instruction, thanks to HyperDbg group members (link)
- Display of the number of blocked context switches in the '.switch' command (link)
- Added support for step-in (the 't' command) in the user debugger (link)
- Added support for step-over (the 'p' command) in the user debugger (link)
- Added support to show all registers or a specific register in the user debugger (link)
- Exported SDK API for running scripts in either the kernel debugger or the user debugger
- Added support to modify registers or a specific register in the user debugger (link)
- Added support to evaluate (run) scripts on the target thread in the user debugger (link)
- Added an indication of a thread's running or paused state to the HyperDbg signature in the user debugger (link)
- Added support for the '.formats' command in the user debugger (link)
- Added support for interpreting parameters based on script engine expressions in the user debugger
- Exported SDK API for evaluating expressions based on the context of the kernel debugger or the user debugger
- Added a new mechanism for showing the 'printf' and the 'print' function messages in the user debugger (link)(link)
Changed
- Non-volatile XMM registers are no longer saved/restored on VM-exit handler (link)
- Fix grammar and spelling errors throughout HyperDbg codebase (link)
- Relocate extension command files into their corresponding VS directory
- Fix infinite VM-exit bug for the '!monitor x' command thanks to @unlockable (link)