Re: [MacPerl] AppleShare IP and MacPerl

[dick@cfcl.com (Dick Karpinski)]

Matthias Ulrich Neeracher <neeri@iis.ee.ethz.ch> writes:
>Mark Meyer <mameyer@xsite.net> writes:
>>In short, I went out there and found MacPerl was running fine unless
>>AppleShare IP was also running. In this case any script would cause MacPerl
>>to crash with a type 2 error when I tried to run it from the menu bar.
>
>I've heard this before, but so far, I was not able to investigate due to the
>lack of an AppleShare IP installation, so I'm still in the dark as to the
>possible causes.

I've used Macintoshes but not debugged low level problems so I
don't understand why serious error aborts like "type n error"
are impossible to get further info from.  Couldn't you slow it
down by some large factor by tracing onto a visible window?

Plan for tracking down Mac error:
 1 - set debug mode
 2 - startup application
 3 - app opens tracing window
 4 - app traces furiously, scrolling by
 5 - terrible condition occurs
 6 - read the last n lines for clues to problem
 7 - enhance app to trace other clues
 8 - start over unless satisfied

Doesn't the debugger make that pretty easy?

It used to be that the problem was that most real programs 
were too big in some resource consumption to accomodate such
direct attacks on their problems.  What makes it hard now?

Dick

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