home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.mac.programmer
- Path: sparky!uunet!think.com!enterpoop.mit.edu!mojo.eng.umd.edu!russotto
- From: russotto@eng.umd.edu (Matthew T. Russotto)
- Subject: Re: Think C debugger problem
- Message-ID: <1992Dec31.225305.15940@eng.umd.edu>
- Date: Thu, 31 Dec 92 22:53:05 GMT
- Organization: Project GLUE, University of Maryland, College Park
- References: <C03K7J.DxJ@rice.edu>
- Lines: 22
-
- In article <C03K7J.DxJ@rice.edu> schmunk@spacsun.rice.edu (Robert Schmunk) writes:
- >An application I have been working on (Think C 4 on a Mac LC II, sys 7)
- >recently developed an inclination to unexpectedly quit and go back to the
- >finder. I had just made a large number of changes so reversing the changes
- >was out of the question and so I just decided to turn on Think C's
- >debugger option. Unhappily, when the application fires up, I get the
- >two debugger windows and everything freezes (reboot necessary). The
- >debugger menu bar is blank and the only clue to the problem is a
- >"Bus error" message in the listing window. Has anybody got any suggestions
- >as to how I can figure out what the problem is? If so, you'll earn my
- >slavish appreciation.
-
- 1) Upgrade to Think C 5.0.4 or (if short on $$$) Think C 4.0.5. 4.0.5
- was the first version to work under System 7, I believe.
-
- 2) Sounds like your project got corrupted. "Remove objects" and
- re-make everything.
- --
- Matthew T. Russotto russotto@eng.umd.edu russotto@wam.umd.edu
- Some news readers expect "Disclaimer:" here.
- Just say NO to police searches and seizures. Make them use force.
- (not responsible for bodily harm resulting from following above advice)
-