🔥Telegram İfşa

This week in the 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…

We regret to clarify that Andreas Zeller will *not* be recording an audiobook of the The Debugging Book and the The Fuzzing Book, 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:

Statistical Debugging! This week in The 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…

Specification Mining! This week in The 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…

Generalizing Failure Circumstances! This week in The 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…

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!

Performance debugging! This week in the 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…

Automatic Repair! This week in the 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.…

Bug tracking! This week in The 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.…

Mining changes and bugs! This week in The 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…

Mission accomplished! The 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 !

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

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

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…

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…

Instructors and students: Do you use The Fuzzing Book or The 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!