News for hackers. Stuff that matters.
Re:Productive Programming by scott_s on Tuesday August 31, 2010 @03:13PM (#1650555)
Indeed. There's also valgrind, which will let you know if you're stomping over memory you shouldn't: http://valgrind.org/

When students come to me with broken C code, I ask two questions: do you know which line it breaks on, and did you run it with valgrind?

There are no comments on this comment yet.