The Debugging Book

IMPORTANT: We will be switching to Mastodon for further announcements. Find and follow us at @TheDebuggingBook" target="_blank" rel="nofollow noopener">mastodon.social/@TheDebuggingB…

Instructors and students: Do you use @FuzzingBook or @Debugging_Book and would like to help shaping their future? If so, fill out our 2024 reader survey at forms.gle/pMDftr94GfLYyJ… and help us find out about our readership!

The Debugging Book 1.2 is out! This version adds support for recent Python versions up to 3.12, and fixes a number of small bugs. Enjoy! debuggingbook.org/html/ReleaseNo…

Debuggingbook 1.1 is out! We * now support (and also require) Python 3.9 or later, * made some optimizations to delta debugging, and * generally made installation of the Python package ("pip install debuggingbook") much easier. Enjoy! debuggingbook.org/html/ReleaseNo…

Some background on the #Alhazen technique: publications.cispa.saarland/3107/ Enjoy!

Automated debugging! Hi folks – we're developing #Alhazen, a tool that automatically finds out when and why your program fails. We'd like you to try it out! If you have a CS degree, know Python, and want to help our research, take part in our user study at vrt-21-0007.cispa.de

We already shared the @FuzzingBook but there is also the @Debugging_Book which focus on automating software debugging, specifically by locating errors and there causes automatically, great read! debuggingbook.org

Debugging at work! Today, I was working on some @Debugging_Book code – and at the very moment I started it, a bug fell off my monitor.

The Debugging Book 1.0 is now available as a Python module. Just do 'pip install debuggingbook' and enjoy! debuggingbook.org/html/Importing…

Mission accomplished! The @Debugging_Book and all its 15 chapters are now complete - from interactive debuggers to slicing and automated repair. Thank you for your continued support and enjoy the read at debuggingbook.org !

Mining changes and bugs! This week in @Debugging_Book, we explore how to mine git repositories and determine which files and functions have seen the most changes – and the most bug fixes. With great interactive visualizations! debuggingbook.org/html/ChangeCou…

Bug tracking! This week in @Debugging_Book, we explore how to systematically track and resolve reported bugs using bug tracking systems. And we discuss bug life cycles, from NEW to FIXED to (hopefully) RESOLVED. Enjoy the read! debuggingbook.org/html/Tracking.…

Automatic Repair! This week in the @Debugging_Book, we show how to automatically repair buggy code, introducing all-new, well-documented + extensible Python code for learning and prototyping. (And yes, it does repair all our examples :-) Enjoy! debuggingbook.org/html/Repairer.…

Performance debugging! This week in the @Debugging_Book, we are exploring how to use (and build!) profilers. Includes visualizations of those parts of your code that take the most time – as always, as downloadable, interactive Python+Notebook code. Enjoy! debuggingbook.org/html/Performan…

We’re taking a short break this week while we’re refining the upcoming chapters on debugging performance issues and -drumroll- automated repair. See you next Tuesday with an all-fresh chapter!

Generalizing Failure Circumstances! This week in @Debugging_Book, we learn how to transform concrete inputs like "2 + 2" into general patterns like "<expr> + <expr>" that capture exactly when the program fails (and can be instantiated into more inputs!): debuggingbook.org/html/DDSetDebu…

Specification Mining! This week in @Debugging_Book, we explore how to learn invariants, types, and other abstractions over multiple runs – and also over failing ones only. (Bonus: how to retrofit type and contract annotations to existing Python code!) debuggingbook.org/html/DynamicIn…

Statistical Debugging! This week in @Debugging_Book, we explore how to determine execution features that correlate with failure, such as code lines executed in failing runs only. Includes colorful visualizations to experiment with right in your browser! debuggingbook.org/html/Statistic…

We regret to clarify that @AndreasZeller will *not* be recording an audiobook of the @Debugging_Book and the @FuzzingBook, as announced on April 1. However, you can achieve the same effect by having your browser read the Web pages aloud, as illustrated in this video:

This week in the @Debugging_Book: Isolating Failure-Inducing Changes! We show how "git bisect" and Delta Debugging isolate code changes that caused a failure, reducing large diffs down to a minimum of changed lines: debuggingbook.org/html/ChangeDeb…