<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Xdebug on Luther Monson</title>
    <link>https://luth.io/tags/xdebug/</link>
    <description>Recent content in Xdebug on Luther Monson</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Mon, 12 Oct 2026 21:10:00 -0700</lastBuildDate>
    <atom:link href="https://luth.io/tags/xdebug/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Step Debugging a Worker That Never Ends</title>
      <link>https://luth.io/blog/2026/10/xdebug-worker-mode/</link>
      <pubDate>Mon, 12 Oct 2026 21:10:00 -0700</pubDate>
      <guid>https://luth.io/blog/2026/10/xdebug-worker-mode/</guid>
      <description>&lt;p&gt;Persistent workers are the big performance win in modern PHP. You boot Laravel or Symfony once, keep the container&#xA;in memory, and serve thousands of requests out of the same process. &lt;a href=&#34;https://github.com/ephpm/ephpm&#34;&gt;ePHPm&lt;/a&gt; has had&#xA;a worker mode for a while. Like most worker runtimes it had a quiet hole in it. You couldn&amp;rsquo;t step debug a request with&#xA;Xdebug. I wanted that fixed without patching Xdebug and without giving up the warm pool. The answer ended up being to&#xA;stop fighting the constraint and route around it. The debug lane is merged on main and coming in the upcoming v0.12.0&#xA;release.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
