<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Gdb on Nick Chandler</title>
    <link>https://nickchandler.dev/tags/gdb/</link>
    <description>Recent content in Gdb on Nick Chandler</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Fri, 03 Apr 2026 19:39:43 -0400</lastBuildDate>
    <atom:link href="https://nickchandler.dev/tags/gdb/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Taking Interruptions in Stride: Debugging an xv6 Lost Wakeup</title>
      <link>https://nickchandler.dev/articles/2026/04/03/taking-interruptions-in-stride-debugging-an-xv6-lost-wakeup/</link>
      <pubDate>Fri, 03 Apr 2026 19:39:43 -0400</pubDate>
      <guid>https://nickchandler.dev/articles/2026/04/03/taking-interruptions-in-stride-debugging-an-xv6-lost-wakeup/</guid>
      <description>&lt;p&gt;A few months ago, I decided to add a stride scheduler to the &lt;a href=&#34;https://www.github.com/mit-pdos/xv6-riscv&#34;  class=&#34;external-link&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;xv6&lt;/a&gt; operating system, to get a better&#xA;understanding of OS schedulers. I wrote a &lt;a href=&#34;https://nickchandler.dev/articles/2025/10/03/lab-report-adding-stride-scheduling-to-xv6/&#34; &gt;blog post&lt;/a&gt; about the experience, including&#xA;my code and how it performed. Toward the end of the post, I mentioned some&#xA;&lt;a href=&#34;https://nickchandler.dev/articles/2025/10/03/lab-report-adding-stride-scheduling-to-xv6/#unexplained-init-process-lockup&#34; &gt;odd behavior&lt;/a&gt; when running my scheduler on a single-core VM. In&#xA;particular, at bootup the OS would hang when starting the initial process. I was able to determine&#xA;that the process had gone to sleep, but wakeups were failing because when they fired, &lt;code&gt;init&lt;/code&gt; was&#xA;still considered an active process. I worked around the issue by removing one of the wakeup&#xA;guard conditions and decided to &amp;ldquo;punt&amp;rdquo; a deeper investigation.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
