I've spent years debugging Windows crashes with tools that were either friendly but limited (e.g. Visual Studio) or powerful but archaic (e.g. WinDbg). I developed patterns and methods for understanding what was going on, and decided to build it into a much more effective debugging tool called ForensicDbg.

I built a modern interface to minimize the friction when debugging. All of the data shown to you is analyzed, interpreted, and presented to you clearly, so you can focus on what matters. Everything is interlinked so you can quickly and intuitivly navigate through the process space.

ForensicDbg comes with an MCP server which allows for agenic debugging. The work done to interpret and interlink your data also benefits AI tools. It removes the risk of hallucinations while building a stable foundation for them to work from without spending tokens.

If you want to try it out you can sign up and get a free beta license here: https://www.forensicdbg.com/beta [Loren_SL]

On these weekends, I was sitting and thinking about where our industry is going, and how fun it was earlier, when we wrote more code than chat messages. The thoughts quickly turned into a wish to build something like we did earlier. In my case, it ended up as something much "earlier" than I had in mind initially...

So, Conway's Game of Life running from a 512-byte x86 boot sector. Maybe you will find it interesting. I tried to comment the code as much as possible, which might be especially useful if you are learning assembly.

Have fun! [0xAX]