There should be a mention of e.g. JTAG -interface. Perhaps a connection to microcontrollers and such also. --Korppi 01:23, 7 November 2005 (UTC)
The illustration should really be C or C++ code, not html. Minor point but that's the geek in me. Nils Jeppe 10:12, 13 March 2006 (UTC)
I agree, and also, why is it simply a picture of code with syntax highlighting? How about showing a picture of an actual debugger running? Perhaps GDB?
I also agree and I have removed it. Something like a command line debugger stepping through a program would be much more relevant. --Avochelm 04:01, 10 August 2006 (UTC)
The word debugging and the word bug are not the same.
Some time ago I added a reference in the "origin" section of this article with the first definition of the word debugging by Myers in 1974. I have not seen any references to the words debug or debugging that are earlier than that. Does anyone know of one?
There are much earlier references to the word bug - the famous Admiral Hopper story in the 1940s and a much earlier reference by Edison in 1878. Fine, but neither reference uses the word debugging so surely they belong in the "Computer bug" article not in this article. Any comments?
Neilm 11:38, 18 May 2006 (UTC)
- I noticed the edit to the article and revised it before I saw this comment. I noticed the same thing you did. Hopefully my edit is close to what you would have done. Feel free to tweak my tweak. ;^) wrp103 (Bill Pringle) 12:55, 18 May 2006 (UTC)
- Thank you, your edits have made this section into one with a much better NPOV. I did tweak it, but just for minor clarification. Neilm 20:10, 18 May 2006 (UTC)
Tools (2nd paragraph)
It is not true that exception handling makes debugging easier. And it is not true, that for example C++ is easier to debug than C because of the existance of exceptions.--09:09, 13 July 2006 (UTC)
- If you have exception handling, you can automatically print out valuable information any time an error occurs. Without it, you have to insert such print outs before the error occurs, which means you have to insert a lot of statements or wait until one occurs and then add the statements (or figure it out from the nature of the error). wrp103 (Bill Pringle) 10:30, 13 July 2006 (UTC)
Wikipedia is not a handbook
Debugging is tiring?
"Debugging is, in general, a cumbersome and tiring task [...]"
This is nonsense. Debugging is neither unwieldy nor inelegant (these are the meanings of "cumbersome") and neither does it necessarily make it tired. Perhaps the poster meant "a time-consuming and tiresome task". I'll change the text accordingly. — Paul G (talk) 16:41, 11 September 2008 (UTC)
Pros to anti-debugging?
Objectivity, not editorializing.
We must strive to be factual and objective, and follow all guidelines, when possible. "Easy" is purely objective, and thus cannot be seen as "factual". The editorializing under the "Tools" section is being removed. GuavaSquash (talk) 05:00, 4 July 2009 (UTC)
Newer Debugging Processes
Debugging functions (grouped lines of code) is problematic because the side-effect of any line can cause multiple other side effects. At exit it will be unknowable which line is offending.
Newer debugging process can step through functions and displays or edit static variables while doing so: but not edit the functions themselves. Watch for a condition is often a feature (used when such a watch would be intrusive in code even optionally, or just freely to find bug).
Higher level code like Mathematical software operates on the bases of freely writing lines and using them in any order. However this is broken when one creates a function: the dubug process again will be unknowable at exit of the function.
CreateModule helps alleviate this by automatically creating functions out of a group of lines, so that while debugging one can both truly edit lines and execute in any order "during runtime" yet not have to separately write (or cut and paste) a group of lines into a function and fun header. — Preceding unsigned comment added by Sven nestle2 (talk • contribs) 22:26, 6 October 2013 (UTC)