Advertisement
Get Stuff Done - For active developers in Linux graphics, kernel, libraries, and more
| Weekly edition | Kernel | Security | Distributions | Search |
| Archives | Calendar | Subscribe | Write for LWN | LWN.net FAQ |
Quotes of the week
Quotes of the week
Posted Feb 7, 2008 21:23 UTC (Thu) by jengelh (subscriber, #33263)Parent article: Quotes of the week
Not having used kgdb makes one learn to write code more carefully over time. At least I have that impression.
(Log in to post comments)
Quotes of the week
Posted Feb 7, 2008 23:11 UTC (Thu) by lutchann (subscriber, #8872) [Link]
Generally I've found kernel debuggers to be most useful for finding bugs in other people's code...
kernel debuggers
Posted Feb 9, 2008 21:35 UTC (Sat) by giraffedata (subscriber, #1954) [Link]
It's the opposite for me. When somebody else's code has a bug, I can often just read the code and see where it doesn't do the right thing. When I wrote the code, I'll miss the bug on reading the code the same way I did when I wrote it.
With the debugger, I have to understand the code intimately. I display a variable value or code path to see if it matches what I intended for it to be. With someone else's code, I don't really know what he intended a variable to mean or what code is supposed to run for what cases, so the debugger isn't much help.
The only place the debugger is especially useful with somebody else's code is when I can't tell from reading the code which piece of it handles my case, so a trace points me to the piece that I need to read more closely.