Re: [MacPerl] The Command-. bug

[Angus McIntyre <angus@pobox.com>]

At 1:04 am +0100 15.01.98, Mark Manning/Muniz Eng. wrote:
>I was trying out a script last night and I hit the
>command-. bug.  Since I have Macsbug installed I typed in
>the STDLOG command to grab the information.  However, when
>I rebooted - the stdlog was empty.  :-(

Sometimes Macsbug can't write to stdlog because the file system is doing
something else; you'll typically see a message like 'File system busy ...'
somewhere on the Macsbug screen if this is the case.

Incidentally, I usually take this as a sign from the gods that I should run
Norton when I come back from the crash; if something goes down while it's
writing a file or directory information, the chances are that the file
system's not going to be in too pretty a state when the dust settles. Such
problems are typically followed by immensely long reboots, indicating that
the Finder's having to work overtime to rebuild its data structures on
disk, but it's quite likely that additional damage may also have been done.
Or at least such has been my experience.

		A

--
angus@pobox.com                                   http://pobox.com/~angus/

    "Sick and twisted would be the first two words that come to mind," he
     said. "But at the same time, it's kind of neat." [Richard Grenier]



***** Want to unsubscribe from this list?
***** Send mail with body "unsubscribe" to mac-perl-request@iis.ee.ethz.ch