Latest gdb important milestone
Multi-core, scripted, cross-platform, ...: gdb 7.0 is dense with buzzword compatibility. It does much more than that, though: it's actually a good value, even for programmers who think they can live without it.
View full article »
Esther Schindler
If the comments are ugly, the code is ugly
claird
SVG a graphics format for 21st century
pasmith
Take Chrome OS for a test spin
Sandra Henry-Stocker
Solaris Tip: Have Your Files Changed Since Installation?
jfruh
Android fragments vs. the iPhone monolith
mikelgan
What Gizmodo missed about the Pro WX Wireless USB disk drive
Sidekick: The Good News & the Bad News
Either way you look at it Microsoft Data Center management did not follow standards or best practices in this failure. In which case it makes me wonder more about the outsourcing of corporate data much less personal data.
- mburton325
Join the conversation here
Quick, practical advice for IT pros. Made fresh daily.
Want to cash in on your IT savvy? Send your tip to tips@itworld.com. If we post it, we'll send you a $25 Amazon e-gift card.
reverse debugging tutorial online
There is an online tutorial for using gdb reverse debugging and process record/replay athttp://www.sourceware.org/gdb/wiki/ProcessRecord/Tutorial
Debuggers?
An alternative to an excellent debugger is excellent design derived from outstanding requirements. The better these are the less likely a debugger needs to be invoked. IMHO many of the root-causes have been distilled down to issues in design or requirements. Any debuggers available for these two important phases....?Debug design? Requirements?
Yes and no. No, there aren't executable debuggers for the overwhelming majority of "requirements" and "designs". Yes, though, there's a vast literature on techniques to formalize and automate analysis and design.
Thanks for raising the question. I'll make a point of covering it in more detail in November 2009. For now, I'll simply offer the tip that the smartest single thing I know to do is to bring in testers and documenters as early in a development cycle as possible. Applications that can't be verified or explained ... well, that stacks the odds against success.