Darwin
November 15th, 2009 by ns7429expected number of hours: 7 hours
actual hours: 11 hours
expected number of hours: 7 hours
actual hours: 11 hours
==7570== Memcheck, a memory error detector.
==7570== Copyright (C) 2002-2008, and GNU GPL’d, by Julian Seward et al.
==7570== Using LibVEX rev 1878, a library for dynamic binary translation.
==7570== Copyright (C) 2004-2008, and GNU GPL’d, by OpenWorks LLP.
==7570== Using valgrind-3.4.0, a dynamic binary instrumentation framework.
==7570== Copyright (C) 2000-2008, and GNU GPL’d, by Julian Seward et al.
==7570== For more details, rerun with: -v
==7570==
…………
OK (12 tests)
==7570==
==7570== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 21 from 1)
==7570== malloc/free: in use at exit: 122,880 bytes in 6 blocks.
==7570== malloc/free: 982 allocs, 976 frees, 193,961 bytes allocated.
==7570== For counts of detected errors, rerun with: -v
==7570== searching for pointers to 6 not-freed blocks.
==7570== checked 124,124 bytes.
==7570==
==7570== LEAK SUMMARY:
==7570== definitely lost: 0 bytes in 0 blocks.
==7570== possibly lost: 0 bytes in 0 blocks.
==7570== still reachable: 122,880 bytes in 6 blocks.
==7570== suppressed: 0 bytes in 0 blocks.
==7570== Rerun with –leak-check=full to see details of leaked memory.
Project 5 went very smoothly.
Google Project: http://code.google.com/p/cs371project5jeffandnicu/
Partner: Jeffery Zhu jz995
predicted number of hours to complete: 3
actual number of hours to complete: 5
TestAllocator.out (as a page)
$ valgrind main.app
==18002== Memcheck, a memory error detector.
==18002== Copyright (C) 2002-2008, and GNU GPL’d, by Julian Seward et al.
==18002== Using LibVEX rev 1878, a library for dynamic binary translation.
==18002== Copyright (C) 2004-2008, and GNU GPL’d, by OpenWorks LLP.
==18002== Using valgrind-3.4.0, a dynamic binary instrumentation framework.
==18002== Copyright (C) 2000-2008, and GNU GPL’d, by Julian Seward et al.
==18002== For more details, rerun with: -v
==18002==
..
OK (2 tests)
==18002==
==18002== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 21 from 1)
==18002== malloc/free: in use at exit: 0 bytes in 0 blocks.
==18002== malloc/free: 71 allocs, 71 frees, 7,613 bytes allocated.
==18002== For counts of detected errors, rerun with: -v
==18002== All heap blocks were freed — no leaks are possible.
==18777== Memcheck, a memory error detector.
==18777== Copyright (C) 2002-2008, and GNU GPL’d, by Julian Seward et al.
==18777== Using LibVEX rev 1878, a library for dynamic binary translation.
==18777== Copyright (C) 2004-2008, and GNU GPL’d, by OpenWorks LLP.
==18777== Using valgrind-3.4.0, a dynamic binary instrumentation framework.
==18777== Copyright (C) 2000-2008, and GNU GPL’d, by Julian Seward et al.
==18777== For more details, rerun with: -v
==18777==
John Doe
Alladin
Jafar
john doe
Jill
Dill
George
Paul
kfjdsklfjs
fdsfdsfds
fdsfsdf
a1
C1
C2
C2
Mr Joe
(W 1/1) John Doe
(W 1/2) Some Guy
(W 2/2) Potato Head
(W 1/1) No Choice
(W 1/4) Big Tie
(W 2/4) Tie Fighter
(W 3/4) Darth Vader
(W 4/4) Dead Extra
A
A
Bob
Joe
==18777==
==18777== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 17 from 1)
==18777== malloc/free: in use at exit: 0 bytes in 0 blocks.
==18777== malloc/free: 1 allocs, 1 frees, 2 bytes allocated.
==18777== For counts of detected errors, rerun with: -v
==18777== All heap blocks were freed — no leaks are possible.
We finished Primes, and we KICKED SOME ASS!!
Our submission runs in 8 ms, whereas Glenn’s takes 10ms.
The way this class is set up is far too complicated. We’re supposed to keep up with dozens of blogs, Twitter, create blogs of our own for others to have to keep up with, create and maintain google code projects, etc. My main issue with all of this is that it’s all too confusing and time consuming. I spent more time figuring out what I need to submit and dealing with all the overhead of how the course is set up than on the actual code. Things like blogs and Twitter feeds have their uses, but IMHO, a programming class such as this isn’t one of them. Google projects is also overkill for this course. For a “project” which can be coded up in a few short hours and easily fits in about 200 lines of actual C++ code (including plenty of comments), there is absolutely no need for bug tracking, and having a powerful versioning system such as svn is almost more overhead than beneficial.
I could go on, but I’m tired of this and I just want to submit it and get it over with.