On Saturday 07 August 2010 00:10:02 John Reiser wrote: > >> 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.
Even with explicit, I don't get anything from valgrind. Compiling with g++ -g -O0 should be enough, right? Anyhow, since I never did any disassembling and that error is not really causing any problems for us, I'll just ignore it for now :) I hoped someone would see a glaring error or something, well thanks anyways. Bye -- Milian Wolff [email protected] http://milianw.de
signature.asc
Description: This is a digitally signed message part.
------------------------------------------------------------------------------ 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
