NetNews Usenet Archive 1992 #16/NN_1992_16.iso/spool/comp/sys/mac/programm/12945

Internet Message Format | 1992-07-23 | 1.8 KB

Path: sparky!uunet!dtix!darwin.sura.net!jvnc.net!rutgers!concert!borg!bach!lari
From: [e-mail] (Humayun Lari)
Newsgroups: comp.sys.mac.programmer
Subject: Re: how to put indelible serial# in resource fork of app?
Message-ID: <[e-mail]>
Date: 23 Jul 92 19:18:28 GMT
References: <[e-mail]> <peter-230792103333@134.7.50.3> <[e-mail]>
Sender: [e-mail]
Organization: University of North Carolina, Chapel Hill
Lines: 27

In article <[e-mail]> [e-mail] (Jon W{tte) writes:
>.50.3> [e-mail] (Peter N Lewis) writes:
>   sake turn macsbug name generation off before you compile it!  I have seen
>   several commercial apps with names turned on in their code checking code,
>   pretty impressive guys :-)
>
>I see MacsBug symbols as a user service ! More than once have I had
>spontaneous crashes, and only the debugger names helped me figure
>out what was going on. Not to mention a dedicated user can provide
>excellent feedback for Tech Support if the names still are in there,
>like, fixing their bugs :-)

Oh, definitely. I was using a release version of a language that should have
stayed in beta for a couple more months -- to be precise, it occasionally
crashed as soon as you tried to run your program. One day, it decided to hang,
and for some inexplicable reason :-) it had been some time since I'd saved.
It was Macsbug time; the only problem was that there was no debugger switch
on the Mac Plus -- it was a public lab, so naturally they didn't want users
accidentally bombing the machine. So <sigh> I stuck the strap of my wristwatch
into the side of the Plus until it hit the switch, looked up the event loop
in Macsbug, and typed something like "g event"...

Amazingly, it worked. :-)


Humayun Lari
([e-mail])