Am Freitag, 6. März 2009 schrieb hce: > Thanks Christoph, you are right, it was a bug. After fixing that, all > read errors are gone. Now it has only errors for > > " Use of uninitialised value of size 8", and "Conditional jump or move > depends on uninitialised value". The "definitely lost: 0 bytes in 0 > blocks", but " possibly lost: 917,938 bytes in 5,594 blocks." > > I guess I don't need to worry too much about above, right? I am going > to further check it.
You have to worry about the "Use of uninitialised value of size 8" and the "Conditional jump or move depends on uninitialised value" errors, because these are often real errors. The possibly lost message does not point directly to an error. But you should check whether the possibly lost memory is expected. Christoph ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
