Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!agate!helios.ee.lbl.gov!ux3.lbl.gov!kushner
From: kushner@ux3.lbl.gov (Gary Kushner)
Newsgroups: comp.sys.ibm.pc
Subject: Turbo Debugger QUESTION
Summary: I can do this with CV easy
Keywords: turbo debug help
Message-ID: <1906@helios.ee.lbl.gov>
Date: 12 Feb 89 05:28:05 GMT
Sender: usenet@helios.ee.lbl.gov
Reply-To: kushner@ux3.lbl.gov
Distribution: comp.sys.ibm.pc
Organization: Lawrence Berkeley Laboratory, Berkeley
Lines: 18

I'm having trouble doing something I think should be relatively easy.
 
When I'm debugging a C program under TD, and I break into it while it's
running, I have a near impossible time getting TD back on track with the
source code.  I always end up in the CPU window.  The trouble is, I've found
no easy way to get TD to execute code until it gets to the start of the next
source line.  I've even traced through the pseudo-code until I've gotten
myself back into known territory and STILL haven't gotten TD to allow me to
trace in the module window.  I've tried many things and won't go into them here,
since I assume the solution is a trivial oversight on my part.
 
I know recovering from an interrupt while in never-never land is not an easy
thing for a debbuger to do, but my inability with TD is all the more
frustrating because of the ease in which CV does it.  In CV, one just sets the
view to source (hit F3 twice) and executes the trace command.

Hope someone knows the answer,
Gary.