-
Notifications
You must be signed in to change notification settings - Fork 14
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
Debug flags #169
base: master
Are you sure you want to change the base?
Debug flags #169
Conversation
This reverts commit 3638513.
All good now! Agressive compiler checks don't give any warning, and we can now easily use the sanitizer to detect many issues at runtime. |
@scemama there is a bug at the compilation step:
|
Sorry... it compiles now :-) |
@scemama thanks! I ran a few tests through valgrind. The C tests look fine though there is one However, on the Fortran test I get the following error: I guess it's an artifact of the Fortran test modifications from PR #168
|
In this statement:
the string returned by I fixed it in the tests by initializing |
Fixed! You can merge now :-) |
Thank you @scemama ! It's interesting that I haven't seen this bug before, I used to run |
If that's OK with you, I prefer to fix the Python determinant tests first in PR #168 and then merge this PR. Nothing to do on your side, I will update this branch when it's done. |
Perfect! |
This PR adds
--enable-debug
and--enable-sanitizer
to configure.ac to make many checks on the library for the github actions.It depends on PR #168
There are still some issues to fix before it can be merged, but I created the draft so that you know that I am working on it.