Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!usc!elroy.jpl.nasa.gov!ncar!midway!news
From: gft_robert@gsbacd.uchicago.edu
Newsgroups: comp.sys.mac.programmer
Subject: Re: THINK C Debugger (was Re: Looking for a Debugger.)
Message-ID: <1990Nov15.194727.18721@midway.uchicago.edu>
Date: 15 Nov 90 20:43:45 GMT
Sender: news@midway.uchicago.edu (News Administrator)
Organization: University of Chicago Graduate School of Business
Lines: 23

----- 

Thanks to all who pointed out that command-D will copy the data to the data
window.

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.

Robert


============================================================================
= gft_robert@gsbacd.uchicago.edu * generic disclaimer: * "It's more fun to =
=            		         * all my opinions are *  compute"         =
=                                * mine                *  -Kraftwerk       =
============================================================================