File Recovery via Core Dump in Debugger?

Discussion in 'Mac Basics and Help' started by honeychurch2, Oct 3, 2012.

  1. honeychurch2 macrumors newbie

    Joined:
    Sep 27, 2011
    #1
    Ok, this morning, I had two unsaved stickies files open, wanted to close one, and hit cmd+w. A dialog box asked me if I wanted to save my changes, and I clicked don't save. This closed both stickies. Normally I would use Time Machine to recover files, but I hadn't created a backup using Time Machine after I created this file.

    I then found a post on the MacResource forums that said this:

    So my question is, would it be at all possible to enable debugging retroactively, do a core dump, and use the file containing the contents of my computer's memory to retrieve my stickies file? And if so, could some kind person please post a link explaining how, or explain how themselves?

    Many thanks!
     
  2. old-wiz macrumors G3

    Joined:
    Mar 26, 2008
    Location:
    West Suburban Boston Ma
    #2
    I have a hard time believing you could enable debugging retroactively.
     
  3. honeychurch2 thread starter macrumors newbie

    Joined:
    Sep 27, 2011
    #3
    D'oh. As per the tech note linked in my original post,
    Didn't see that the first time around, and thought there was a way to enable debugging retroactively.

    So that doesn't help me then. If I understand correctly, I would have had to start the debugging process before I created my Stickies files, and then once I lost the files, gone back and enabled core dumps?

    Sorry if my questions seem a bit ignorant. I consider myself tech-savvy, but this is new territory for me.
     
  4. honeychurch2 thread starter macrumors newbie

    Joined:
    Sep 27, 2011
    #4
    Just an update that may prove helpful to anyone wanting to recover files from a core dump: I asked a few people more knowledgeable about this stuff than I am, and basically what they said was that it's possible that the contents of the file may be able to be extracted, but only with the program's source code, or its debugging symbols. Neither of which I have, of course. Not to mention that I don't have time to learn how to use GDB, or increase my extremely limited knowledge of Obj-C. While I could look for ASCII strings that represent the lost data, it's really not worth that much trouble.

    I hope this info proves useful for someone else, though.
     

Share This Page