Path: utzoo!dciem!trigraph!john From: john@trigraph.UUCP (John Chew) Newsgroups: comp.sys.mac.programmer Subject: Re: Core Dump Message-ID: <399@trigraph.UUCP> Date: 17 Aug 88 17:50:52 GMT Article-I.D.: trigraph.399 References: <136@lloyd.camex.uucp> Reply-To: poslfit@gpu.utcs.toronto.edu (John J. Chew) Organization: Trigraph Inc., Toronto, Canada Lines: 21 Summary: use Macsbug 6.0 "LOG" In article <136@lloyd.camex.uucp> kent@lloyd.camex.uucp (Kent Borg) writes: >Is there a way from Macsbug to do a "core dump" to disk? Recently when >pasteing some text into uw, my Macintosh Plus crashed. Using Macsbug I >managed to find (3 copies of) my text and copy 3 pages by hand. Using Macsbug 6.0B1, enter the "LOG pathname" command to open a log file on disk. Dump the relevant portion of memory in hex dump format using "DM". Close the log file ("LOG"). Then use your favourite word processor to strip the hex, keep the ASCII and restore formatting. A caveat: periodically, the LOG command creates an empty file instead of a log. I do not know what causes this -- for reference, I am using a Mac 512E with 2M (Dove) RAM, Dove SCSI and a CMS 60M external drive. John -- -- john j. chew, iii poslfit@utorgpu.bitnet trigraph, inc. poslfit@gpu.utcs.toronto.edu toronto, canada {uunet!mnetor!utzoo,utgpu,utcsri}!trigraph!john [it is my opinion that these are solely my opinions.]