Skip to content

research: MemorySanitizer or equivalent built in to debug mode #1471

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.

Sign up for GitHub

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

Jump to bottom
Open
andrewrk opened this issue Sep 4, 2018 · 2 comments
Open

research: MemorySanitizer or equivalent built in to debug mode #1471

andrewrk opened this issue Sep 4, 2018 · 2 comments
Labels
enhancement Solving this issue will likely involve adding new logic or components to the codebase. research This proposal requires a considerable amount of investigation before it can be considered.
Milestone
0.16.0

Comments

@andrewrk
Copy link
Member

andrewrk commented Sep 4, 2018 •
edited
Loading

Here's an example bug #1446

This issue is to investigate MemorySanitizer and do something like it or an idea inspired by it. The idea is to detect loads and stores of undefined or otherwise invalid memory and treat them as safety violations.

Ideally the performance penalty would be small enough that we would include it in ReleaseSafe mode as well as Debug mode.
@andrewrk andrewrk added enhancement Solving this issue will likely involve adding new logic or components to the codebase. contributor friendly This issue is limited in scope and/or knowledge of Zig internals. labels Sep 4, 2018
@andrewrk andrewrk added this to the 0.4.0 milestone Sep 4, 2018
@bmeh
Copy link

bmeh commented Sep 8, 2018

Can the AddressSanitizer be used also, if you are not using it already? It would be nice to know if there's a way to know anything about both sanitizer's performance penalty in relation to Zig.

I hope it will not be included in ReleaseFast though, or at the very least one should be able to disable those completely.

@andrewrk
Copy link
Member Author

andrewrk commented Sep 9, 2018 •
edited
Loading

It would certainly not be in ReleaseFast or ReleaseSmall builds.

I think I was actually thinking of AddressSanitizer, not MemorySanitizer, but I'll let this issue be to investigate both of them.

@andrewrk andrewrk modified the milestones: 0.4.0, 0.5.0 Sep 28, 2018
@andrewrk andrewrk modified the milestones: 0.5.0, 0.6.0 Apr 12, 2019
@andrewrk andrewrk removed the enhancement Solving this issue will likely involve adding new logic or components to the codebase. label Apr 12, 2019
@andrewrk andrewrk modified the milestones: 0.6.0, 0.7.0 Dec 31, 2019
@andrewrk andrewrk removed the contributor friendly This issue is limited in scope and/or knowledge of Zig internals. label Oct 9, 2020
@andrewrk andrewrk modified the milestones: 0.7.0, 0.8.0 Oct 9, 2020
@andrewrk andrewrk modified the milestones: 0.8.0, 0.9.0 Nov 6, 2020
@SpexGuy SpexGuy added the enhancement Solving this issue will likely involve adding new logic or components to the codebase. label Mar 20, 2021
@andrewrk andrewrk modified the milestones: 0.9.0, 0.10.0 May 19, 2021
@andrewrk andrewrk added the research This proposal requires a considerable amount of investigation before it can be considered. label Aug 10, 2021
@jcalabro jcalabro mentioned this issue Jun 8, 2023
Open
@mlugg mlugg added this to Safety Aug 22, 2024
@mlugg mlugg moved this to To do in Safety Aug 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement Solving this issue will likely involve adding new logic or components to the codebase. research This proposal requires a considerable amount of investigation before it can be considered.
Projects
Safety
Status: To do
Milestone
0.16.0
Development

No branches or pull requests
3 participants
@andrewrk @SpexGuy @bmeh