I'm not sure what you're asking for (as programs don't need — and usually just don't — represent the data they're processing in memory the same way they're stored on disk. Data in memory is organized to facilitate processing, data on disk (files) is optimized for interoperability, storage size, or some other reason; and they are transformed from one form to the other when loading or writing files. Even if they are alike, it's probably the other way around: Files are then just memory content written to disk and just as unreadable.
The website to the book Mac OS X Internals provides a description and program on how to dump core of running processes, i.e. write the main memory associated with a particular process to disk.
If you want to compile it on OS X Lion using Apple's developer tools, remove the
-arch <name> arguments to
gcc from the
You can then run
sudo ./gcore <pid>, with
<pid> as displayed e.g. in Activity Monitor. Open the resulting dump file e.g. in a hex editor to view it. On my system, a rather simple process like Calculator produces files of around 450MB in size.