Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!samsung!uunet!stanford.edu!neon.Stanford.EDU!mrhoten
From: mrhoten@neon.Stanford.EDU (Matthew Paul Rhoten)
Newsgroups: comp.sys.mac.programmer
Subject: Think C/7.0FC1
Summary: Ka-blam
Keywords: think c 4.04
Message-ID: <1991May3.002915.29453@neon.Stanford.EDU>
Date: 3 May 91 00:29:15 GMT
Reply-To: mrhoten@cs.Stanford.EDU
Distribution: na
Organization: Computer Science Department, Stanford University
Lines: 26

OK, here's the setup: I'm using a Macintosh SE/30, running 7.0FC1, and
Think C 4.04 with the new MPW-ish interfaces.

Here's the problem: a project containing one C source file which itself
contains "main() {}" crashes sporadically at runtime trying to access some
chunk of memory that's way towards the 4 gigabyte addressable limit. 
On occasion I'll get information in the debugger about a 'scod' event,
so I'm wondering whether this is an incompatibility with the new high-level
events.

From what I can tell, running the program outside of the environment or
using the debugger fixes the problem, but I'm not certain.

Does anyone else have problems like this? The number of reboots I'm being
required to make is rather annoying. The project in question uses high-level
events to communicate between two or possibly three processes. I'm not going
to wimp out and use some hack to get it to work, so going back to 6.0.x and
the old interfaces isn't really a viable option.

Great compiler, though.
 -matt


-- 
Matt Rhoten             | PO Box 10031       | Standard disclaimers apply.
mrhoten@cs.stanford.edu | Stanford, CA 94309 | (415) 497-2853 | veni vidi vomui