Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!usc!bbn.com!nic!chaos.cs.brandeis.edu!chaos!phils From: phils@chaos.cs.brandeis.edu (Phil Shapiro) Newsgroups: comp.sys.mac.programmer Subject: Re: THINK C Debugger (was Re: Looking for a Debugger.) Message-ID: Date: 14 Nov 90 15:05:04 GMT References: <1990Nov13.223209.16268@midway.uchicago.edu> Sender: @chaos.cs.brandeis.edu Organization: Symantec Corp. Lines: 38 In-Reply-To: gft_robert@gsbacd.uchicago.edu's message of 13 Nov 90 23:26:19 GMT In article <1990Nov13.223209.16268@midway.uchicago.edu> gft_robert@gsbacd.uchicago.edu writes: Speaking of the THINK C debugger: It's a pretty nice graphical source-level debugger. BUT it seems really kludgy in many ways, at least compared to the THINK Pascal debugger. My main beef is having to type in the variables I wish to examine. I HATE this, particularly since these variable names aren't kept around between runnings of the program in development. This considerably lengthens the edit-run-debug-edit cycle. (Or does someone know a way to keep them around?). If you select an expression in the data window (any expression that doesn't have a function call), you can copy it to the data window by using Command-D. Much better is THINK Pascal's method of having all variables immediately available for examination, and having variables for different procs in different places in the debugger window. In THINK C I tend to end up with 5 windows each named "*theTable" (for example), each tracking a variable thru the call chain. I typically make a lot of use of the "clear" key to remove windows (or data window entries). Also, if you want to reevalute an expression in a different context, you can use the "Set Context" menu item. I happen to prefer the Think C debugger for a number of reasons (I hate scrolling through tons of local or global variables, I often want to have many structures expanded, etc.) I suppose in a perfect environment we could pick and choose the particular interface pieces we like best. -phil -- Phil Shapiro Technical Support Analyst Language Products Group Symantec Corporation Internet: phils@chaos.cs.brandeis.edu