Valgrind 1.0.0 Released

Anonymous Lazy Boy writes "Yesterday saw the official release of Valgrind 1.0.0. Valgrind is a C/C++ programmer's dream come true: effortless memory allocation checking, uninitialized memory access, leaks etc. Purify for Linux has arrived, only better: contrary to its commercial (non-Linux) sibling, checking is performed directly on the executable, no re-linking necessary. The technology behind Valgrind is highly fascinating and explained down to the very gory details in the documentation."

Comments

recursivity

[alvi]

Hum,

[chicken]~> vagrind valgrind

seems to work ok. But valgrinding a valgrinded valgrind causes some ugly errors and asks for a bug report. Well, I know this isn't fair. :)

Anyways, this looks like a really sweet tool.

Re:What's the fun in that?

[Greg Lindahl]

I am neither trolling nor stupid, and I don't find Purify that useful. I am also not as insulting to people who don't agree with me.

In the 60's, we programmed in Fortran, and debugged with PRINT statements.

In the 70's, we programmed in Pascal, and debugged with WRITE statements.

In the 80's, we programmed in C, and debugged with printf statements.

In the 90's, we programmed in C++, and debugged with >>.

Re:Strangeness

[idealego]

Trolls are busy at work today I see.

I actually wasted about 15 minutes looking into this.

Re:What's the fun in that?

[MisterBlister]

In the 80's, we programmed in C, and debugged with printf statements. In the 90's, we programmed in C++, and debugged with >>.

So you *are* stupid after all!

Re:If you're worried about threading/memory bugs

[adam_megacz]

you obviously have no idea what you're talking about

$ grep Megacz /usr/src/gcc-3.1/MAINTAINERS

Adam Megacz adam@xwt.org

Yeah, I probably know absolutely nothing about gcj...

Re:If you're worried about threading/memory bugs

[10Ghz]

0wn3d!