-
Notifications
You must be signed in to change notification settings - Fork 23
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
Run yosys and plugin with address sanitizer #649
Comments
I think this gets more important as we can find crashes that might not be detected otherwise (like the use-after-delete situation in chipsalliance/yosys-f4pga-plugins#366) |
I don't have permission to assign owners to bugs in this repo, so CC: @rkapuscik @tgorochowik |
Related: #98 |
Possible blocker: chipsalliance/Surelog#3661 I had some troubles in making ASAN work due to lack of support for code loaded with dlopen/dlclose, but I was able to use it after all with the help of this workaround: google/sanitizers#89 (comment) |
Running the tests with address sanitizer ( clang doc: https://clang.llvm.org/docs/AddressSanitizer.html ; should be similar for gcc/clang) will help finding some issues early.
It does result in somewhat slower binaries (but much less so than e.g. valgrind), so the CI machines will have to work harder, but any findings here will well offset the engineering time attempting to find a head-scratching issue later.
The text was updated successfully, but these errors were encountered: