pho@dilow.esd.sgi.com (Paul Ho) (09/28/90)
Has anyone experience any problems when running macbugs with Think C? I don't know what version of macbugs I have (I think it is 6.1). I am running Think C 4.0. Sometimes when I quit from an application which was started within Think C, macbugs would kick in and tell me that there was a bus error. The funny thing about it is that it doesn't happen all the time, and it doesn't happen when I build the application and run it under the (Multi)Finder. If you have any ideas, I would appreciate it. Thanks. +-------------------------------------------------------------------+ | You Are | Paul Ho | | What You Do | Silicon Graphics Inc. | | When It Counts. | dilow.esd.sgi.com!pho | +-------------------------------------------------------------------+
Chris.Gehlker@p12.f56.n114.z1.fidonet.org (Chris Gehlker) (10/02/90)
> Has anyone experience any problems when running macbugs with Think C? > I don't know what version of macbugs I have (I think it is 6.1). I am > running Think C 4.0. Sometimes when I quit from an application which > was started within Think C, macbugs would kick in and tell me that > there was a bus error. The funny thing about it is that it doesn't > happen all the time, and it doesn't happen when I build the application > and run it under the (Multi)Finder. If you have any ideas, I would > appreciate it. Thanks. Sounds like what happened to me when I wasn't carefull about calling unloadseg(). Actually, I was carefull at first but then I moved a routine. The segment was never actually being unloaded under MF since by default Think C makes a pretty big SIZE -1 resource but I did get unloC evelopment environment. -- Uucp: ...{gatech,ames,rutgers}!ncar!asuvax!stjhmc!56.12!Chris.Gehlker Internet: Chris.Gehlker@p12.f56.n114.z1.fidonet.org