<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Debugging on Bulrush Labs — Richard Tibbetts</title><link>https://bulrushlabs.com/articles/tag/debugging/</link><description>Recent content in Debugging on Bulrush Labs — Richard Tibbetts</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 29 Aug 2010 22:13:00 +0000</lastBuildDate><atom:link href="https://bulrushlabs.com/articles/tag/debugging/index.xml" rel="self" type="application/rss+xml"/><item><title>Non-Destructive Process Inspection on OSX: Blog Post Recovery</title><link>https://bulrushlabs.com/articles/2010/08/29/non-destructive-process-inspection-on-osx-blog-post-recovery/</link><pubDate>Sun, 29 Aug 2010 22:13:00 +0000</pubDate><guid>https://bulrushlabs.com/articles/2010/08/29/non-destructive-process-inspection-on-osx-blog-post-recovery/</guid><description>&lt;p&gt;Moments ago I was writing a different blog post, about home renovation. Unfortunately just as I posted it a bug in ecto, the aging client I still use to edit blog posts, caused the complete loss of the text with no backup copies. Because messing about with system tools is more fun than rewriting that blog post, I present instead a brief howto for creating a core dump on OSX without killing a process, and inspecting that core dump to attempt to recover your data.&lt;/p&gt;</description></item></channel></rss>