<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Pdb on Nalar</title>
    <link>https://nalar.dev/tags/pdb/</link>
    <description>Recent content in Pdb on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 09 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/pdb/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Attach pdb to Running Python Processes in Python 3.14</title>
      <link>https://nalar.dev/attach-pdb-to-running-python-processes/</link>
      <pubDate>Wed, 09 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/attach-pdb-to-running-python-processes/</guid>
      <description>&lt;p&gt;A Python service can misbehave without crashing. A worker may loop unexpectedly, a request may remain in an odd state, or a long-running process may hold data that is difficult to reproduce in a development environment.&lt;/p&gt;&#xA;&lt;p&gt;Historically, using &lt;code&gt;pdb&lt;/code&gt; in that situation usually required planning ahead. You could add &lt;code&gt;breakpoint()&lt;/code&gt; to the code, start the program under the debugger, or restart it with extra instrumentation. Those approaches are useful, but they do not help much when the interesting state already exists inside a running process.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
