To do a memory, or core dump on os x you'd need to launch the rev app yourself, 
instead of letting the os handle it (eg. via "launchctl", using the "limit" 
subcommand). Alternatively, you'd need to enable core dumping (disabled by 
default) by some other means.  You then terminate the rev process, most likely 
using "kill" by supplying a fault, like "SIGSEGV". Finally you'd need to find, 
decipher and interpret the dumped data.

So basically it's diving down deep into the unix shell bowels and muck around 
there. I cobbled these ideas together based on the following links, and haven't 
tried anything myself:

http://developer.apple.com/mac/library/documentation/Darwin/Reference/ManPages/man5/core.5.html
http://developer.apple.com/Mac/library/documentation/Darwin/Reference/ManPages/man1/launchctl.1.html
http://en.wikipedia.org/wiki/Signal_(computing)

On 17 Mar 2010, at 15:19, Lyn Teyla wrote:

> Richmond Mathewson wrote:
> 
>> Yup: just tried to open what sits inside the MacOS folder inside one of my 
>> Devawriter standalones
>> with HexEdit - no joy: well, from a selfish point of view this makes me 
>> rather happy - no nosey-parkers
>> getting very far with bits of my stuff I wish to keep private . . .  :)
> 
> UNLESS they do a "memory dump" - whatever that is. :(



-- 

official ChatRev page:
http://bjoernke.com?target=chatrev

Chat with other RunRev developers:
go stack URL "http://bjoernke.com/chatrev/chatrev1.3b3.rev";

_______________________________________________
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution

Reply via email to