Enable memtrace on F* #3016
Merged
Enable memtrace on F* #3016
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
This commit brings memtrace into F* to do memory profiling. It is (always) linked to F*, but does not do anything unless the MEMTRACE environment variable is set, so this should be zero-overhead (except for a few kb of binary size) when memtrace is not used. When used, the overhead is still supposed to be in the low digits of %. With this enabled, we can just run MEMTRACE=trace.ctf fstar.exe .. to obtain a trace.ctf file with information about the allocations. This can then be inspected with the memtrace-viewer tool (installed separately, since it's quite big). I think having this enabled by default would be useful, and the cost seems pretty low. Some more info: https://blog.janestreet.com/finding-memory-leaks-with-memtrace/ http://web.archive.org/web/20230528123929/https://blog.janestreet.com/finding-memory-leaks-with-memtrace/
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.
This commit brings memtrace into F* to do memory profiling. It is (always) linked to F*, but does not do anything unless the MEMTRACE environment variable is set, so this should be zero-overhead (except for a few kb of binary size) when memtrace is not used. When used, the overhead is still supposed to be in the low digits of %.
With this enabled, we can just run
MEMTRACE=trace.ctf fstar.exe ..
to obtain a trace.ctf file with information about the allocations. This can then be inspected with the memtrace-viewer tool (installed separately, since it's quite big).
I think having this enabled by default would be useful, and the cost seems pretty low.
Some more info:
https://blog.janestreet.com/finding-memory-leaks-with-memtrace/
http://web.archive.org/web/20230528123929/https://blog.janestreet.com/finding-memory-leaks-with-memtrace/