Use extreme assertion for metadata mapped assert #812
Merged
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.
The
assert_metadata_mapped
method uses themmap
system call and expects a failure. This is too costly even for debug builds. We disable it unless the "extreme_assertions" feature is enabled.This issue has a greater impact on VMs that use the valid-object bit (VO bit) metadata because the metadata is accessed on every object allocation, and there is such an assertion in metadata access.
The
rr
debugging tool seems to record every system call. This PR also makesrr
much faster (e.g. 14.20s vs 0.202s when running hello world in Ruby).How to test
Compile mmtk-core with debug build, and use
strace
to run the VM. Before this PR, a hello world program in Ruby (using mmtk-ruby) shall have 400000+mmap
invocations returning -1 witherrno = EEXIST
; with this PR, they will all disappear.