Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!udel!rochester!pt.cs.cmu.edu!o.gp.cs.cmu.edu!andrew.cmu.edu!vd09+ From: vd09+@andrew.cmu.edu (Vincent M. Del Vecchio) Newsgroups: comp.sys.mac.programmer Subject: Re: THINK C Debugger (was Re: Looking for a Debugger.) Message-ID: Date: 16 Nov 90 22:28:59 GMT References: <1990Nov15.194727.18721@midway.uchicago.edu> Organization: Carnegie Mellon, Pittsburgh, PA Lines: 22 In-Reply-To: <1990Nov15.194727.18721@midway.uchicago.edu> > Excerpts from netnews.comp.sys.mac.programmer: 15-Nov-90 Re: THINK C > Debugger (was R.. gft_robert@gsbacd.uchica (1092) > OK, here's my other main beef: since the THINK C debugger is a separate > program, why must it exit -- thus losing all your breakpoints, variable > windows you've set up, etc -- every time you stop running the program > you're debugging? OK, I'm sure that there is a valid reason for this, so let me turn the > question around: why isn't there a way to save project specific things > such as breakpoints, variables you want shown, etc. from debug session > to debug session? I'm sure this would be tricky since the source is > going to change, but there must be some better way than setting > everything up from scratch again. Personally, I would be happy if you could just save the set of variable windows. As you noted, the source can change quite a bit. Maybe they could add something to the _editor_ to handle breakpoints, kind of like the way it's done in Think Pascal. Vince Del Vecchio vd09@andrew.cmu.edu