<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Debugging on Selectivity.net</title>
    <link>https://selectivity.net/tags/debugging/</link>
    <description>Recent content in Debugging on Selectivity.net</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 24 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://selectivity.net/tags/debugging/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Selectivity Makes Large Bug Reports Easier to Understand</title>
      <link>https://selectivity.net/selectivity-makes-large-bug-reports-easier-to-understand/</link>
      <pubDate>Sat, 24 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://selectivity.net/selectivity-makes-large-bug-reports-easier-to-understand/</guid>
      <description>&lt;p&gt;A minimal reproducer is a small example that still demonstrates a problem. It gives the person investigating a bug less material to read and fewer irrelevant details to carry through each experiment. Getting there is often laborious. You remove a group of rows, rerun the program, discover that the failure has vanished, restore the rows and try a smaller group. It is useful work, just rather repetitive.&lt;/p&gt;&#xA;&lt;p&gt;Selectivity turns that routine into a search driven by a predicate. The predicate is a command that answers whether the particular behavior survives in the candidate input. Selectivity begins with larger deletions and works toward smaller ones when necessary. Each successful deletion becomes the new starting point. Eventually the engine reaches individual units, such as one line or one file, and checks whether removing any of them still preserves the predicate.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
