<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Sanitizers on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/sanitizers/</link>
    <description>Recent content in Sanitizers on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 21 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/sanitizers/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Memory Safety Tools: AddressSanitizer vs Valgrind vs ThreadSanitizer vs UBSan</title>
      <link>https://www.pistack.xyz/posts/2026-06-21-memory-safety-sanitizers-addresssanitizer-valgrind-threadsanitizer-ubsan/</link>
      <pubDate>Sun, 21 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-06-21-memory-safety-sanitizers-addresssanitizer-valgrind-threadsanitizer-ubsan/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;Memory bugs — buffer overflows, use-after-free, data races, and undefined behavior — are among the most difficult and dangerous categories of software defects. They can cause silent data corruption, crashes that manifest hours later on a different code path, and security vulnerabilities that persist for decades. The 2022 CWE Top 25 lists out-of-bounds writes and use-after-free as the #1 and #7 most dangerous software weaknesses.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
