>> What is the shortest source-code test case that reproduces this problem?
> I don't get it... this code doesn't show any problems in valgrind for me: > > http://mwolff.pastebin.com/JxCgvtK9 The short test case shows that memcheck "knows" about utimes(). Suspicion now turns to the compiler/linker. I see that the original code has an 'explicit' keyword but the short test case does not. If memcheck still does not complain after enlarging the short test case to contain 'explicit', then there must be some other differences. Finding them may require disassembling the generated code and/or single-stepping the execution. -- ------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
