Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uwm.edu!ux1.cso.uiuc.edu!peltz
From: peltz@cerl.uiuc.edu (Steve Peltz)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Why am I getting bus-error in think C debugger?
Message-ID: <1990Nov27.204831.29340@ux1.cso.uiuc.edu>
Date: 27 Nov 90 20:48:31 GMT
References: <7022@vax1.acs.udel.EDU>
Sender: news@ux1.cso.uiuc.edu (News)
Organization: UIUC Computer-based Education Research Lab
Lines: 17

In article <7022@vax1.acs.udel.EDU> bach@vax1.udel.edu (Baskaran Subramaniam) writes:
>I am new to programming in Think C.  Could someone tell me what a bus-error
>means?  When I try to step through a test program (which runs without
>giving any error outside the debugger) I get a bus-error. Why?     

If it doesn't give any errors outside the debugger, then it is unlikely to
be a problem with resources not being found or invalid pointers (though still
possible). One guess, though. Are you using Macsbug?

Trying to use a newer version of Macsbug than what came with THINK C 3.0 didn't
work when using the THINK C Debugger. I forget the details, but either tracing
or breakpoints would trap out to Macsbug rather than the THINK C Debugger. No
such problems when using the version that came with it (Macsbug 5.4, I believe,
that plots a fractal if run as an application).
--
Steve Peltz
Internet: peltz@cerl.uiuc.edu	PLATO/NovaNET: peltz/s/cerl