Valgrind log for 2009-04-09 (binary version e52354656db48e840748556e9ed44b37)

Case number:671071-985920
Topic:Game: Other
Opened by:gringer
Status:Closed
Type:Suggestion
Opened on:Thursday, April 9, 2009 - 01:06
Last modified:Friday, April 10, 2009 - 18:39

Hello,

I'm attaching a valgrind log (memory access check) for foldit, carried out on Thu, 09 Apr 2009 ~12:50 +1200. I started up the program using valgrind and clicked quit as early as possible (i.e. at the connect online/offline screen) to generate this log:

$ valgrind ./Foldit 2>&1 | gzip > valgrind_foldit_$(date --iso).txt.gz

Here are the summaries from the bottom of the log:

==5530== ERROR SUMMARY: 153298 errors from 711 contexts (suppressed: 2744 from 9)
==5530== malloc/free: in use at exit: 22,516,102 bytes in 37,579 blocks.
==5530== malloc/free: 224,118 allocs, 186,541 frees, 81,071,266 bytes allocated.
==5530== For counts of detected errors, rerun with: -v
==5530== Use --track-origins=yes to see where uninitialised values come from
==5530== searching for pointers to 37,579 not-freed blocks.
==5530== checked 25,564,780 bytes.
==5530==
==5530== LEAK SUMMARY:
==5530== definitely lost: 22,788 bytes in 164 blocks.
==5530== possibly lost: 48,344 bytes in 1,356 blocks.
==5530== still reachable: 22,444,970 bytes in 36,059 blocks.
==5530== suppressed: 0 bytes in 0 blocks.

Hope this helps,

David Eccles (gringer)

(Thu, 04/09/2009 - 01:06  |  1 comment)


admin's picture
User offline. Last seen 46 weeks 6 days ago. Offline
Joined: 11/10/2007
Groups: vi users
Status: Open » Closed
Type: Bug » Suggestion

Thanks, gringer. We're running our own valgrind logs now.

Sitemap

Developed by: UW Center for Game Science, UW Institute for Protein Design, Northeastern University, Vanderbilt University Meiler Lab, UC Davis
Supported by: DARPA, NSF, NIH, HHMI, Amazon, Microsoft, Adobe, Boehringer Ingelheim, RosettaCommons