* johannes hanika <[email protected]> [07-01-13 04:54]: > the summary only is not really enough to tell anything from it. full text > is more useful. in this case tons of false positives in opencl and > rawspeed. some warnings about uninitialized memory being accessed, which is > probably some unclean initialization, we've had that before. most of the > time it's just a padding word to be memcpyd with the rest which has no > effect regardless of the value. nothing about memory leaks though? > > > * Patrick Shanahan <[email protected]> [06-30-13 21:18]: [...] > > Another test failed with: > > > > ==30792== More than 10000000 total errors detected. I'm not reporting any > > more. > > ==30792== Final error counts will be inaccurate. Go fix your program! > > ==30792== Rerun with --error-limit=no to disable this cutoff. Note > > ==30792== that errors may occur in your program without prior warning from > > ==30792== Valgrind, because errors are no longer being displayed. > > ==30792== > > > > full text: > > http://wahoo.no-ip.org/~pat/darktable.mem.txt
Was this not helpful? Do you need it to run again? -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535 @ http://linuxcounter.net ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _______________________________________________ Darktable-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/darktable-users
