Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!usc!wuarchive!uunet!isis!cla
From: cla@isis.cs.du.edu (Chuck Anderson)
Newsgroups: comp.os.msdos.programmer
Subject: Re: Turbo C++ (Debugger bug?)
Keywords: reentrant routines
Message-ID: <1990Dec11.222033.21473@isis.cs.du.edu>
Date: 11 Dec 90 22:20:33 GMT
References: <25804@uflorida.cis.ufl.EDU>
Reply-To: cla@isis.UUCP (Chuck Anderson)
Organization: Center for Life Fulfillment
Lines: 24

In article <25804@uflorida.cis.ufl.EDU> jdb@reef.cis.ufl.edu (Brian K. W. Hook) writes:
>I have Turbo C++ 1.00 but have noticed that it has a couple of errors, ie.
>bugs.  Has anyone encountered the fact that the debugger REALLY screws up
>when tracing code?  It seems that it arbitrarily jumps to come code at
>times that resembles other code.  For example:

What I have noticed is the debugger getting confused with reentrant routines.
If I am on a statement within proc A, that calls routine B, which happens to
call proc A, the debugger's next step is the next line in proc A (The statement
following the call to proc B.), but it is the second instance of the call
that is now being traced.

I suppose that it would be difficult for the debugger to determine that this 
set of events have taken place. But it is confusing because there's no obvious 
indication that you are now tracing through another (the second) instance of 
the routine.

Know whadda mean?

-- 
  *************************************************************************
     Chuck Anderson                uucp    :         uunet!isis!cla 
     Boulder, Co. (303) 494-6278   internet:         cla@isis.cs.du.edu 
  *************************************************************************