Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!iuvax!cica!tut.cis.ohio-state.edu!zaphod.mps.ohio-state.edu!van-bc!ubc-cs!fornax!mcdonald
From: mcdonald@fornax.UUCP (Ken Mcdonald)
Newsgroups: comp.sys.mac.programmer
Subject: Help, weird THINK C bombs
Message-ID: <1@fornax.UUCP>
Date: 14 Feb 90 01:53:27 GMT
Distribution: na
Organization: School of Computing Science, SFU, Burnaby, B.C. Canada
Lines: 13

Is the first version of THINK C 4.0 known to have problems resetting globals
to what they are supposed to be, when it exits?  I've finally gotten around
to using my copy, and have found that while it causes no problems while
running, it virtually always causes an attempted launch o a succeeding
program to blow up--producing some VERY interesting screen effects.  (If
a programs gonna crash, at least it should make the experience interesting!)
I admit, I am running somewhat of a kamikaze system, and it could be an
interaction with an init--but only THINK C causes this problem.  Any
suggestions?

Thanks,
Ken McDonald
{mcdonald@cs.sfu.ca}