On Sunday, 1. August 2010 19:32:34 John Reiser wrote: > > http://gitorious.org/kdevelop/kdevelop/blobs/master/languages/cpp/include > > pathresolver.cpp > > I agree that the code at line 90: > explicit FileModificationTimeWrapper( const QStringList& files = > QStringList(), const QString& workingDirectory = QString() ) : m_newTime( > time(0) ) does seem to initialize m_newTime, and therefore the code from > line 119: times[0].tv_sec = m_newTime; > times[0].tv_usec = 0; > times[1].tv_sec = m_newTime; > times[1].tv_usec = 0; > would initialize all of the array times[2], and thus the complaint by > memcheck about times() on line 124 would indicate some problem with > memcheck's understanding of utimes(), or a compiler problem with the > initialization of m_newTime. > > 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 :( -- 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
