I am using valgrind-3.8.1 on Fedora 18, 32 bit x86, and am linking fortran libraries to my main C++ code. It seems that when malloc'd values end up being initialized in fortran code, that this is still tagged by valgrind as uninitialized data. I have worked around (avoided) this problem by initializing new memory to 0. I have seen related posts on the net, but am not sure if this is already flagged as a bug, or if I am not using valgrind correctly with fortran.
smime.p7s
Description: S/MIME Cryptographic Signature
------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev
_______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
