Update windows syscall table with the correct min/max versions #2556
Conversation
This file contains hidden or 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
derekbruening
approved these changes
Jun 13, 2025
Contributor
derekbruening
left a comment
derekbruening
left a comment
There was a problem hiding this comment.
Thank you for the PR!
Contributor
|
Looks like Github is refusing to run the Ubuntu 20.04 VM test jobs: #2548 covers updating them. Unfortunately the testing is thus not in a good place. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This pull request updates
drsyscall/table_windows_ntoskrnl.cto include correct minimum and maximum Windows versions for several syscalls.These changes were generated via a script (with the help of j00ru with the actual x86 syscall tables) so their might be a minor inaccuracy or two, but overall it should be correct, this update should have no functional impact on Dr. Memory's behavior.
Note: Due to the current absence of specific macros in Dr. Memory that precisely define every Windows service pack or update, some entries might use broader version ranges. For instance, if you see an entry like
(WINVISTA,WINVISTA), please interpret this as the syscall being present from the initial release of Windows Vista (SP0) up to its final service pack (SP2). This reflects the highest achievable precision with existing definitions.See also #1909