New & Revolutionary Debugging Techniques?

An anonymous reader writes "It seems that people are still using print statements to debug programs (Brian Kernighan does!). Besides the ol' traditional debugger, do you know any new debugger that has a revolutionary way to help us inspect the data? (don't answer it with ddd, or any other debugger that got fancy data display), what I mean is a new revolutionary way. I have only found one answer. It seems that Relative Debugging is quite neat and cool."

Relative debugging, an idea whose time has come

[Red Warrior]

I have some relatives who demonstrate numerous error conditions.

Right...

[Anonymous Coward]

So you already have to have a program that does what your program does in order to check it.

Ever think of deploying that one?

Polyheaded Debugger

[N8F8]

The technique I've found most effective is to run many simultaneous debugging sessions in parallel. My debugger of preference is a semi-autonomous intelligent agent that seeks out defects in a random fashion. I call this type of agent a "user".

Re:Exceptions

[eyeye]

Line numbers? What next.. fire?

Re:Print statements work fine for me, too

[Charles Dart]

I use humorous print statements e.g. in a loop i will put in

echo 'bork! ';

....ahh, good times.

Relative debugging?

[some guy I know]

To use relative debugging ...

I don't see how relative debugging can work at all.
I mean, most of my relatives don't know anything about computers, much less debugging.

Re:Hey, nice ad!

[moexu]

"Always code as if the person who ends up maintaining your code will be a violent psychopath who knows where you live." -- Martin Golding

Re:Polyheaded Debugger

[Anonymous Coward]

"My debugger of preference is a semi-autonomous intelligent agent .... a 'user'"

You have intelligent users?