<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Debugging on Bits, Trades &amp; Systems</title>
    <link>https://blog.turboawesome.win/tags/debugging/</link>
    <description>Recent content in Debugging on Bits, Trades &amp; Systems</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 04 Oct 2023 09:35:00 +0000</lastBuildDate>
    <atom:link href="https://blog.turboawesome.win/tags/debugging/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Go&#39;s Race Detector in CI: Catching Data Races Before They Catch You</title>
      <link>https://blog.turboawesome.win/2023/10/gos-race-detector-in-ci-catching-data-races-before-they-catch-you/</link>
      <pubDate>Wed, 04 Oct 2023 09:35:00 +0000</pubDate>
      <guid>https://blog.turboawesome.win/2023/10/gos-race-detector-in-ci-catching-data-races-before-they-catch-you/</guid>
      <description>Data races are among the hardest bugs to find and reproduce. Go&amp;#39;s built-in race detector finds them automatically — if you run it. Here&amp;#39;s how to integrate it into CI effectively and what to do when it fires.</description>
    </item>
    <item>
      <title>Profiling Go Services in Production with pprof</title>
      <link>https://blog.turboawesome.win/2020/04/profiling-go-services-in-production-with-pprof/</link>
      <pubDate>Wed, 01 Apr 2020 10:18:00 +0000</pubDate>
      <guid>https://blog.turboawesome.win/2020/04/profiling-go-services-in-production-with-pprof/</guid>
      <description>Go&amp;#39;s pprof tooling is built in, low-overhead, and more useful than most engineers realise. Here&amp;#39;s how to capture CPU and memory profiles from production services and actually read what they tell you.</description>
    </item>
    <item>
      <title>Reading GC Logs Like a Detective</title>
      <link>https://blog.turboawesome.win/2017/04/reading-gc-logs-like-a-detective/</link>
      <pubDate>Tue, 18 Apr 2017 09:11:00 +0000</pubDate>
      <guid>https://blog.turboawesome.win/2017/04/reading-gc-logs-like-a-detective/</guid>
      <description>GC logs are the most information-dense diagnostic output the JVM produces, and most engineers never learn to read them properly. A guide to interpreting G1GC logs and using them to diagnose real production problems.</description>
    </item>
    <item>
      <title>Heap Dumps and Flight Recorder: Diagnosing JVM Memory Problems in Production</title>
      <link>https://blog.turboawesome.win/2016/08/heap-dumps-and-flight-recorder-diagnosing-jvm-memory-problems-in-production/</link>
      <pubDate>Wed, 24 Aug 2016 14:55:00 +0000</pubDate>
      <guid>https://blog.turboawesome.win/2016/08/heap-dumps-and-flight-recorder-diagnosing-jvm-memory-problems-in-production/</guid>
      <description>Heap dumps and Java Flight Recorder are the two tools that diagnose production JVM memory problems. Understanding how to capture them without killing the service, and how to read what they tell you, is a gap in most JVM engineers&amp;#39; toolkits.</description>
    </item>
  </channel>
</rss>
