Path: utzoo!attcan!uunet!tut.cis.ohio-state.edu!bgsuvax!denbeste
From: denbeste@bgsuvax.UUCP (William C. DenBesten)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Wishlist for THINK _C_ (4.1 ? 5.0 ?)
Message-ID: <5655@bgsuvax.UUCP>
Date: 12 Apr 90 14:57:45 GMT
References: <17184@well.sf.ca.us>
Organization: Bowling Green State University B.G., Oh.
Lines: 26

In article <16903@well.sf.ca.us> nilesinc@well.UUCP (Avi Rappoport) writes:
> What I really need is a way to keep my breakpoints and variables between
> runs of the program.  So annoying to have to keep resetting them.

From article <17184@well.sf.ca.us>, by mjf@well.sf.ca.us (Marty Fried):
> I too was frustrated with that aspect of the debugger.  I have just discovered
> that you can use the "skip to here" function to re-run from any point, even 
> from the beginning.

Skip to here is neat, but keep in mind as you use it that the value of
variables is NOT changed back to what it was at that point in the
execution.  For example, if you are stopped at c: and skip to a:, the
value printed the second time is 9, not 7.

      x=7;
   a: printf("x is %d\n",a);
      x=9;
   c:

It is not reasonable to expect the debugger to change the value of
variables back since that would require keeping enormous amounts of
state information. This does, however, mean that you can get really
wierd results.

-- 
William C. DenBesten   is   denbeste@bgsu.edu  or   denbesten@bgsuopie.bitnet