Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!wuarchive!psuvax1!rutgers!usenet!ogicse!qiclab!percy!tektronix!reed!bowman
From: bowman@reed.UUCP (Eric Bowman)
Newsgroups: comp.sys.mac.programmer
Subject: Re: What's System Error 12, exactly?
Message-ID: <16299@reed.UUCP>
Date: 6 Apr 91 00:21:11 GMT
References: <670554754.1@mmug.fidonet.org> <1991Apr5.011516.23646@athena.mit.edu>
Reply-To: bowman@reed.UUCP (Eric Bowman)
Organization: Reed College, Portland OR
Lines: 18

In article <1991Apr5.011516.23646@athena.mit.edu> captkidd@athena.mit.edu (Ivan Cavero Belaunde) writes:
>A fairly common reason for SysErr 12 is, I've found, running a pgm with a
>Debugger() or DebugStr() statement in it without a debugger installed. It's
>a little less likely than other suggestions that I've seen out here (Mac II
>specific code, for instance) but possible. Either way, though, the obvious
>suggestion is to install a debugger in the Plus. Then if it is a Debugger()
>statement it will break into the monitor, and if it's not it will break anyway
>and you'll be able to look at the trap # and look it up. Hope this helps.

This was the problem...which raises another question?: Why doesn't a _Debugger
trap bring up the funky old debugger in rom?

later,
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
BoBo                                                 Ready, Willing, & Abelian
bowman@reed.{edu,bitnet,uucp}
"I think that there is a moral to this story, namely that it is more important
to have beauty in one's equations than to have them fit experiment." - Dirac