Fix breakpointexception problem #326
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Sorry, I didn't see the question.
Yes, it is. Generally, we shouldn't read the memory directly from VMX-root mode. However, reading using HyperDbg memory routines like |
Merged
SinaKarvandi
added a commit
that referenced
this pull request
Dec 19, 2023
## [0.7.1.0] - 2023-12-20 New release of the HyperDbg Debugger. ### Changed - Fix the single core broadcasting events issue ([link](ab95cd7)) - Evaluate the '.pagin' ranges as expressions ([link](ab95cd7)) - Add hexadecimal escape sequence as string parameter for string functions ([link](60fbec6)) - Add hexadecimal escape sequence as wstring parameter for wstring functions ([link](e6dbc3f)) - Fix breakpoint and the '!epthook' problems in the same address ([link](#326))
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
would cause debugger to get stuck. The reason is that
DebuggingCallbackHandleBreakpointExceptiondoesn't handle 0xcc if there is an event at the rip address.BTW, is it always safe to read RIP's byte without checking whether is valid in
IdtEmulationHandleExceptionAndNmi?