3 comments

  • Cieric1 hour ago
    I feel like it&#x27;s good to note since I missed it. This post is from Feb 13, 2023. He has up to 8 posts on this at this point which don&#x27;t appear to be linked to from this post. I think linking to all of them would be a bit much, but they&#x27;re all currently listed on his main page [1].<p>[1] <a href="https:&#x2F;&#x2F;www.timdbg.com&#x2F;" rel="nofollow">https:&#x2F;&#x2F;www.timdbg.com&#x2F;</a>
  • whartung39 minutes ago
    A favorite developing a debugger story was from a friend of mine.<p>They were working on a debugger for OS&#x2F;2, which was quite notable at the time for being multitasking.<p>And at one point they got to enough of a base feature set that they could use the debugger on itself. Debugging the debugger.<p>While debugging the debugger, they would inevitably encounter other bugs in the debugging debugger.<p>So, with OS&#x2F;2, they had a bit of an epiphany when they were able to debug the debugger debugging the debugger.
    • sroussey16 minutes ago
      It took us a bit of work back in the day to use Firebug to debug Firebug. But pretty easy these days to have Chrome dev tools to debug itself.
  • scott011 hour ago
    There’s a relevant book from No Starch, highly recommend. The author also has a series of blog posts on the topic.<p><a href="https:&#x2F;&#x2F;nostarch.com&#x2F;building-a-debugger" rel="nofollow">https:&#x2F;&#x2F;nostarch.com&#x2F;building-a-debugger</a>