Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!sdd.hp.com!spool.mu.edu!snorkelwacker.mit.edu!bloom-picayune.mit.edu!athena.mit.edu!captkidd
From: captkidd@athena.mit.edu (Ivan Cavero Belaunde)
Newsgroups: comp.sys.mac.programmer
Subject: Re: What's System Error 12, exactly?
Message-ID: <1991Apr5.011516.23646@athena.mit.edu>
Date: 5 Apr 91 01:15:16 GMT
Article-I.D.: athena.1991Apr5.011516.23646
References: <670554754.1@mmug.fidonet.org>
Sender: news@athena.mit.edu (News system)
Organization: Massachusetts Institute of Technology
Lines: 28

In article <670554754.1@mmug.fidonet.org> Jim.Spencer@p510.f22.n282.z1.fidonet.org (Jim Spencer) writes:
>>Eric Bowman writes in a message to All
>EB> Does anyone have any suggestions for what might cause a System 
>EB> Error 12? IMII says it's an "Unimplemented Core Routine: An unimplemented 
>EB> trap number was encounted." 
>EB> It only happens inside a printing loop, on an app run over a 
>EB> network, on a Mac Plus. Everything works fine on a Mac II, heap 
>EB> scrambling or no. It's compiled for a 68000; written in MPW C++, 
>EB> and compiled using C 3.2b1 (optimizer on -- might this be the 
>EB> problem?) 
>EB> Any suggestions would be greatly appreciated.

#undef LURK

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.

As an aside, I wanted to thank andy@treehouse.UUCP for his helpful response on
navigating the extent B-Tree and stuff. I tried mailing, but it bounced.

#define LURK

-Ivan