Path: utzoo!utgpu!watserv1!watmath!att!att!linac!pacific.mps.ohio-state.edu!zaphod.mps.ohio-state.edu!usc!snorkelwacker.mit.edu!paperboy!husc6!bunny!bunny.gte.com!CAH0
From: CAH0@bunny.gte.com (Chuck Hoffman)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Why am I getting bus-error in think C debugger?
Message-ID: <10078@bunny.GTE.COM>
Date: 20 Nov 90 14:16:54 GMT
References: <7022@vax1.acs.udel.EDU>
Sender: news@GTE.COM
Organization: GTE Laboratories, Inc.
Lines: 23

In article <7022@vax1.acs.udel.EDU> bach@vax1.acs.udel.EDU (Baskaran 
Subramaniam) writes:
> 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?

Could be that you trying to open a resource which is not visible to the 
debugger.  The debugger assembles code and puts it into the project file, 
named something like name.pi, where pi is the Greek character you get with 
option-p.  If you have other resources, they must be put into 
name.pi.rsrc (not name.rsrc); the naming convention is rigid.
If the resource is 
somewhere else, you will get a bus error before you can check for a good 
handle.  You also can get bus errors if you mix stdio calls, like printf, 
with QuickDraw routines, like DrawString.  Good luck.  I'm new, too, and 
the bus error problems were very frustrating.


- Chuck Hoffman, GTE Laboratories, Inc.  |  I'm not sure why we're here,
cah0@bunny.gte.com                       |  but I am sure that while we're
Telephone (U.S.A.) 617-466-2131          |  here, we're supposed to help
GTE VoiceNet: 679-2131                   |  each other.
GTE Telemail: C.HOFFMAN                  |