Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!rphroy!caen!kuhub.cc.ukans.edu!maverick.ksu.ksu.edu!iowasp.physics.uiowa.edu!ns-mx!umaxc.weeg.uiowa.edu!drenze
From: drenze@umaxc.weeg.uiowa.edu (Douglas Renze)
Newsgroups: comp.sys.mac.programmer
Subject: THINK C 4.0's debugger, System 7, and you.
Message-ID: <5617@ns-mx.uiowa.edu>
Date: 20 Apr 91 21:41:36 GMT
Sender: news@ns-mx.uiowa.edu
Reply-To: drenze@umaxc.weeg.uiowa.edu (Douglas Renze)
Organization: U of Iowa, Iowa City, IA
Lines: 23

I have a question about THINK C.  Please pardon me if this has already been
addressed (& point me to the answer), but I've just begun reading this news-
group.
	I've been using System 7.0FC1 for some time now, but I seem to have
some problems with compatibility with THINK C's debugger (I use THINK C
4.0).  I try to run something under the debugger, and it freezes the system.
The only message I get is 'odd address' in the debugger window, then it goes
down.  I thought that this might be because I was using MacsBug, too, but when
I took it out of my system folder & rebooted, the same thing still happened.
	FYI, I use System 7.0FC1 on a Mac SE, 4 M RAM, INITs/CDEVs/etc: MacsBug,
AfterDark.
	Has anybody else experienced this?  Is this an "official" bug?  Is there
a patch that fixes this?

BTW, where can I get a patch to whatever the latest version of THINK C is (I
think it's 4.0.4, no?)

Thanx in advance.  Please reply to me, and if there's enough interest, I'll
summarize and post to the net.

Peace and Long Life,

Doug