|
| This Article | ||
| ||
| Share | ||
| Bibliographic References | ||
| Add to: | ||
| | ||
| Search | ||
| ||
| ASCII Text | x | ||
| Diomidis Spinellis, "Debuggers and Logging Frameworks," IEEE Software, vol. 23, no. 3, pp. 98-99, May/June, 2006. | |||
| BibTex | x | ||
| @article{ 10.1109/MS.2006.70, author = {Diomidis Spinellis}, title = {Debuggers and Logging Frameworks}, journal ={IEEE Software}, volume = {23}, number = {3}, issn = {0740-7459}, year = {2006}, pages = {98-99}, doi = {http://doi.ieeecomputersociety.org/10.1109/MS.2006.70}, publisher = {IEEE Computer Society}, address = {Los Alamitos, CA, USA}, } | |||
| RefWorks Procite/RefMan/Endnote | x | ||
| TY - MGZN JO - IEEE Software TI - Debuggers and Logging Frameworks IS - 3 SN - 0740-7459 SP98 EP99 EPD - 98-99 A1 - Diomidis Spinellis, PY - 2006 KW - debugging KW - breakpoint KW - logging framework VL - 23 JA - IEEE Software ER - | |||
DOI Bookmark: http://doi.ieeecomputersociety.org/10.1109/MS.2006.70
Debuggers are cheap and effective tools. Typically we use them in a bottom-up fashion starting from the problem going to its source, but when this strategy fails, we might have to resort to a more tedious top-down breadth-first search. To locate bugs, we can also use hardware-assisted data and code breakpoints. For bugs that are difficult to reproduce, attaching a debugger to a running process as well as postmortem and remote debugging are some alternatives. Finally, we can permanently embed debugging knowledge in a program's source code, through logging statements.
Index Terms:
debugging, breakpoint, logging framework
Citation:
Diomidis Spinellis, "Debuggers and Logging Frameworks," IEEE Software, vol. 23, no. 3, pp. 98-99, May-June 2006, doi:10.1109/MS.2006.70
Usage of this product signifies your acceptance of the Terms of Use.

