Be notified of new releases
Create your free GitHub account today to subscribe to this repository for new releases and build software alongside 28 million developers.Sign up
Externally noticeable changes
- Bug ids for Access Violation exceptions have been standardized to the
<bug type id>:<memory details>[<size>][<offset>]. This
includes bug ids for guard page access exceptions, as
STATUS_GUARD_PAGE_VIOLATIONexceptions are just a sub-type of
STATUS_ACCESS_VIOLATION. bug type ids
DEPhave been changed
AVEto simplify things.
- Text descriptions for Access Violation exceptions should now all follow the
- Determining if an Access Violations happened near the stack is now more
precise by relying on the actual virtual allocation for the stack to
determine what memory range is part of the stack.
- Determining the integrity level of a process was throwing unpredictable
exceptions. Since I do not care much about this information and have little
time to fix it, I've opted to disable the code and not put the integrity
level in the report anymore.
- I've renamed more time related variables to include "InSeconds" in the name.
- Test coverage has been improved by allowing you to trigger Access Violations
in memory regions with specific properties (i.e. unallocated memory, reserved
memory, inaccessible memory, and guard pages). Tests have been rebuild with
VS 2017 and latest Win 10 SDK.