Path: utzoo!attcan!uunet!wuarchive!sdd.hp.com!ucsd!dog.ee.lbl.gov!pasteur!agate!shelby!csli!ramaley
From: ramaley@csli.Stanford.EDU (Alan Ramaley)
Newsgroups: comp.sys.mac.programmer
Subject: 'am I dead yet?', or, debugging
Message-ID: <15998@csli.Stanford.EDU>
Date: 24 Oct 90 17:54:19 GMT
Organization: Center for the Study of Language and Information, Stanford U.
Lines: 27

Okey dokey.  I'm using a Mac SE with Think C 4.0.

I spent my entire summer working on a text editor for the blind.  It's
purty cool, with interruptable speech (thanx Berkeley), goofy
selection tools, etc., etc.  It's a huge program, uses dozens of
objects, sprawls, eats up memory, includes about 50 files, etc.

The problem?  Everytime I run it, it crashes at some point.  And it
crashes completely, that is, the think C debugger breaks, I don't even
get a 'bus error' or anything like that.

The program has grown beyond the point of comprehension.  I would step
through with the debugger, but the problem could be anywhere, and it
usually takes five minutes or so to show up.

Is there any way to...

(1)	Have Think C generate quietly a list of code it executes, so
that when the program explodes, I can look in this file, and try to
figure out the last line it executed before the crash, or at least
figure out what code file the crash was in?

(2)	Figure out where you are in the program using the debugger?

I'm sure this kind of program-sprawl-can't-find-the-offending-code
problem has struck others.  Could you share your solutions?
							--Alan