Path: utzoo!attcan!uunet!zaphod.mps.ohio-state.edu!usc!ucsd!ogicse!mintaka!bloom-beacon!hstbme.mit.edu!ahodgson
From: ahodgson@hstbme.mit.edu (Antony Hodgson)
Newsgroups: comp.os.msdos.programmer
Subject: Long wait times with Borland's integrated debugger
Summary: invoking the call stack function on large programs takes ages
Message-ID: <1990Oct30.184443.2766@athena.mit.edu>
Date: 30 Oct 90 18:44:43 GMT
Sender: daemon@athena.mit.edu (Mr Background)
Reply-To: ahodgson@hstbme.mit.edu.UUCP (Antony Hodgson)
Organization: Massachusetts Institute of Technology
Lines: 25

I bought TC++ a couple of months ago and have generally been pleased
with it.  I have noticed, however, a very annoying delay when I invoke
the call stack (Ctrl-F3) while debugging a program of about 20,000 lines.
On my 12MHz 286 machine (1MB RAM, 32MB hard disk), it can take upwards of
a minute (*YES, 60 SECONDS*) before the call stack info is displayed.
In the interim, there seems to be a great deal of disk activity.  Even
after I get control back, any subsequent command such as trying to use
the cursor keys to see more of the current line or moving down to the next
line takes another 15, 20, or 45 seconds to respond, and if I make the 
mistake of pressing a cursor key long enough for it to autorepeat, I don't
get control back for several minutes. 

Is this normal (i.e., has this happened to other people)?  Is there anything 
I can do to improve the response time (I already invoke TC++ with the 
extended memory switch, so it has the full 384K available, as confirmed by 
the Get Info menu choice under the File menu item)?  

Any help anyone can give me would be very much appreciated as the current
situation makes it practically impossible to debug my programs efficiently.
Please reply via Email.

Thanks,

Tony Hodgson
ahodgson@hstbme.mit.edu