Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!apple!usc!cs.utexas.edu!uunet!unhd.unh.edu!kepler.unh.edu!pss1
From: pss1@kepler.unh.edu (Paul S Secinaro)
Newsgroups: comp.os.os9
Subject: Diffs between OS-9 2.2 / 2.4 ?
Message-ID: <1991Jun27.140054.13331@unhd.unh.edu>
Date: 27 Jun 91 14:00:54 GMT
Sender: usenet@unhd.unh.edu (USENET News System)
Organization: University of New Hampshire
Lines: 33
Nntp-Posting-Host: kepler.unh.edu


     Recently, we have been having trouble with a piece of software
which we are evaluating.  When I run the program on our system, which
is running OS-9/68020 v2.2, I get an error #000:102, which the manual
states is a "Bus exception error" or something like that (it does not
go into any more detail than that).  This same binary is known to run
properly on a system running OS-9 v2.4 on a 68030 module.

So, my questions boil down to:

1.  What exactly does error #000:102 mean?  I know that UNIX, for
example, will give a "Bus Error - core dumped" message if you try to
use an improperly initialized pointer or otherwise bang up against the
limits imposed by the MMU.  Does it mean the same thing in OS-9?  Or
is it referring to some sort of hard error on the processor bus?

2.  Could this type of error be caused by lack of upward compatibility
from v2.2 => v2.4 of OS-9.

3.  Could this program be trying to execute '030 specific code on the
'020?  Can the Microware C compilers generate '030 specific code?

    I realize that it's impossible for anyone to fully answer any of
these questions without knowing a lot about the code itself.  I'm just
interested in knowing if 1,2, and 3 are possible sources of trouble.
Is there any way to setup DEBUG to go active on an error trap, or does
it do this automatically (I've never used it much before).  Thanks

Paul
-- 
Paul Secinaro             | Synthetic Vision and Pattern Analysis Laboratory
pss1@kepler.unh.edu       | Department of Computer and Electrical Engineering
p_secinaro@unhh.unh.edu   | University of New Hampshire     (603) 862-3287