Path: utzoo!attcan!uunet!know!sdd.hp.com!uakari.primate.wisc.edu!aplcen!haven!mimsy!mojo!russotto
From: russotto@eng.umd.edu (Matthew T. Russotto)
Newsgroups: comp.sys.mac.programmer
Subject: Re: 'am I dead yet?', or, debugging
Message-ID: <1990Oct25.174509.10250@eng.umd.edu>
Date: 25 Oct 90 17:45:09 GMT
References: <15998@csli.Stanford.EDU>
Sender: news@eng.umd.edu (The News System)
Organization: College of Engineering, Maryversity of Uniland, College Park
Lines: 26

In article <15998@csli.Stanford.EDU> ramaley@csli.Stanford.EDU (Alan Ramaley) writes:

>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...

>(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?


Things get much better if you can localize the crash to a set of procedures--
I think that using the profile code, you can get a list of procedures 
executed to be output.  


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