Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!unix.cis.pitt.edu!pitt!amanue!oglvee!jr From: jr@oglvee.UUCP (Jim Rosenberg) Newsgroups: comp.os.os9 Subject: Faulting address on bus errors? Message-ID: <623@oglvee.UUCP> Date: 28 Nov 90 17:17:30 GMT Distribution: comp Organization: Oglevee Computer Systems, Connellsville, Pa Lines: 23 We sell greenhouse control systems that use a VME-based M68000 running OS-9 in ROM. The systems have been out in the field for a couple of years and are quite stable, but we would now like to back and beef up our error handling. If we get a bus error, we would like to be able to know the address where the exception occurred. The normal exception handler provided by the OS-9 shell doesn't provide this information, but the debugger does. (We don't currently have the debugger loaded in our ROM's.) Reading the Motorola book, the information we want is clearly and unambiguously saved on the Supervisor Stack when a bus error occurs. The problem is how to get to it. The OS-9 manual writeup of F$STrap says that a routine installed this way is executed in *user* state. In giving the interface to such a routine they don't indicate anywhere that you have access to *system* stack. Is there a way to get access to the exception frame pushed onto the system stack by the hardware? Any other workaround? Any help would be appreciated. Please reply by mail; we don't get a full feed of this newsgroup. -- Jim Rosenberg #include --cgh!amanue!oglvee!jr Oglevee Computer Systems / / 151 Oglevee Lane, Connellsville, PA 15425 pitt! ditka! INTERNET: cgh!amanue!oglvee!jr@dsi.com / /