Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

tests fail on recent win10 machines due to lack of baked-in syscall info #2273

Closed
derekbruening opened this issue Mar 7, 2020 · 0 comments · Fixed by #2280
Closed

tests fail on recent win10 machines due to lack of baked-in syscall info #2273

derekbruening opened this issue Mar 7, 2020 · 0 comments · Fixed by #2280
Assignees

Comments

@derekbruening
Copy link
Contributor

Tests like drsyscall_test and drstrace_test fail on my win10 1909 machine: drsys fails to initialize, b/c the 1909 info is not baked in. All the tests will need to have auto-generation added.

@derekbruening derekbruening self-assigned this Mar 7, 2020
derekbruening added a commit that referenced this issue Mar 9, 2020
Adds use of a sysnum file generated by a prior Dr. Memory test to the
drmf tests which use dryscall.  #2279 covers a better long-term solution.

Fixes #2273
derekbruening added a commit that referenced this issue Mar 9, 2020
Adds use of a sysnum file generated by a prior Dr. Memory test to the
drmf tests which use dryscall.  #2279 covers a better long-term solution.

Fixes #2273
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant