-
Notifications
You must be signed in to change notification settings - Fork 0
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
Memory issues detected by valgrind #1
Comments
you have a proposed fix ? |
Not yet ! |
Looking again I found that after commenting out this line on
|
Looking again the correct place to comment the offending line is in |
it's odd that this would make a difference, except in that valgrind requires dynamic linking to inject its shared libraries overriding malloc and friends... otoh forcing a static build probably isn't that good of an idea; it should be up to the user configuring the build. |
Yes I agree with you, I don't see the point to link the compiler libraries statically by default. |
Valgrind can be very rigorous. There are some algorithms which work fine using uninitialized data and valgrind will complaint about this. The classical example is sparse sets https://www.geeksforgeeks.org/sparse-set/ |
it should be up to the user deciding whether he wants the binary statically or dynamically linked. related: #1
On a fresh build of this project and executing it under valgrind gives this result:
The text was updated successfully, but these errors were encountered: