c - Are there known false positives issues with Valgrind? -
Is there a known false positivity with Valgrind? I get a 'conditional jump' or 'lieutenant', which with the fmemopen function, writes in C and compiles with GCC. Am I sure that this is true?
EDIT: Are there issues that are not in suppression files? Are there things that can do in a program that are not really errors, but Valgrind will say that they are? If there are known issues, then a list would be good.
Yes, there are false positivities with Valgrind, therefore, for example, special Gilgit and GCC versions There are suppression files for If you are using old valgrind with new GCC and glybic, then the valve can be positive, i.e. with valgrind 3.3 with Gibbic 2.9.
After saying this, you still have to look into this issue and know that it is actually a false positive (if this is the case, you can write suppression for yourself) Or is it a genuine bug in your program?
There is no quick and easy way to say what is going on here, but in this case I suspected that you are passing the initial value without your code library code Valgrind option < Try code> - track-origins = yes . It will show where the initial value came from. If this is your code, then you probably should start it. If it is inside the library, then it may be mis-positive or still, the library may be due to poor values of call arguments, so check them out.
Comments
Post a Comment