Slashdot Mirror
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."
I have some relatives who demonstrate numerous error conditions.
"If, therefore, any be unhappy, let him remember that he is unhappy by reason of himself alone."
~Epictetus
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?
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".
"God fights on the side with the best artillery." - Napoleon, Marshal of France - speaking truth to power
Line numbers? What next.. fire?
Bush and Blair ate my sig!
I use humorous print statements e.g. in a loop i will put in
....ahh, good times.
echo 'bork! ';
I mean, most of my relatives don't know anything about computers, much less debugging.
Those who sacrifice security to condemn liberty deserve to repeat history or something. - Benjamin Santayana
"Always code as if the person who ends up maintaining your code will be a violent psychopath who knows where you live." -- Martin Golding
"Seek first to understand." - Socrates