Reading 13: Debugging
Sometimes you have no choice but to debug – particularly when the bug is found only when you plug the whole system together, or reported by a user after the system is deployed, in which case it may be hard to localize it to a particular module. For those situations, we can suggest a systematic strategy for more effective debugging.
Reading 13: Debugging Reading 13: Debugging Software in 6.031 Safe from bugs Easy to understand Ready for change Correct today and correct in the unknown future. Communicating clearly with future programmers, including future you. Designed to accommodate change without rewriting. Objectives The topic of today’s class is systematic debugging. Sometimes you have no choice but to debug – particularly when the bug is found only when you plug the whole system together, or reported by a user after the system is deployed, in which case it may be hard to localize it to a particular module. For those s
Explore this link on the map →related reading
- Reading 9: Debuggingweb.mit.edu
- The Debugger's Toolkit - by Addy Osmani - Elevateaddyo.substack.com
- CSC 151 - Hypothesis-driven debuggingeikmeier.sites.grinnell.edu
- Computers can be understood - Made of Bugsblog.nelhage.com
- A Bunch of Programming Advice I'd Give To Myself 15 Years Ago | Marcus' Blogmbuffett.com
- Transcript – Debugging: Techniques for Uncertain Times – Chelsea Troychelseatroy.com
- Reading 9: Avoiding Debuggingweb.mit.edu
- Debugging Misadventures: Down the Rabbit Holejamie-wong.com
- Some ways to get better at debuggingjvns.ca
- CS106B Backtracking Warmupweb.stanford.edu
- Stepping through code and inspecting variables to isolate bugs | Apple Developer Documentationdeveloper.apple.com
- Your Debugger Sucksrobert.ocallahan.org