Xref: utzoo comp.unix.aux:2793 comp.sys.mac.programmer:17559
Path: utzoo!attcan!uunet!aplcen!haven!mimsy!mojo!russotto
From: russotto@eng.umd.edu (Matthew T. Russotto)
Newsgroups: comp.unix.aux,comp.sys.mac.programmer
Subject: Re: THINK C for A/UX?
Message-ID: <1990Sep19.171117.14704@eng.umd.edu>
Date: 19 Sep 90 17:11:17 GMT
References: <1990Sep19.012057.5581@bushido.uucp>
Sender: news@eng.umd.edu (The News System)
Organization: College of Engineering, Maryversity of Uniland, College Park
Lines: 21

In article <1990Sep19.012057.5581@bushido.uucp> mnowak%bushido.uucp@umich.edu (Michael A. Nowak) writes:
>I've started using A/UX 2.0 and have just started trying to work with THINK C
>in this environment (I've used THINK C extensively in the regular MacOS
>environment).  THINK C 4.0 exhibits some strange behavior under A/UX:
> 
>o  The debugger always complains that it is out of memory, despite changes in
>   the size of its Multifinder partition size.

That's better results than I have-- the debugger merely crashes.

>o  After running a project and returning to the THINK C environment, the whole
>   THINK C application just quits, with no explanation.  There's usually a
>   5 to 10 second period between returning from the run and the exit where
>   THINK C appears to run preoperly.

Is this with or without the debugger?  I've had no problems running without
the debugger.

--
Matthew T. Russotto	russotto@eng.umd.edu	russotto@wam.umd.edu
      .sig under construction, like the rest of this campus.