Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site topaz.ARPA
Path: utzoo!watmath!clyde!bonnie!akgua!mcnc!decvax!genrad!panda!talcott!harvard!seismo!columbia!topaz!@RUTGERS.ARPA:goun%cadlac.DEC@decwrl.ARPA
From: @RUTGERS.ARPA:goun%cadlac.DEC@decwrl.ARPA
Newsgroups: net.works
Subject: Finding multiple bugs in one pass
Message-ID: <743@topaz.ARPA>
Date: Fri, 22-Feb-85 11:23:31 EST
Article-I.D.: topaz.743
Posted: Fri Feb 22 11:23:31 1985
Date-Received: Wed, 27-Feb-85 04:43:55 EST
Sender: daemon@topaz.ARPA
Organization: Rutgers Univ., New Brunswick, N.J.
Lines: 23

From: goun%cadlac.DEC@decwrl.ARPA  (Roger H. Goun)

> I'm not looking to bring back the memory dump.  What I *would* like
> to see, though, is some form of interactive debugging which promotes
> the finding of more than one bug in a run.  No, I don't have any
> suggestions.

Even in an interactive environment, fixing, recompiling, and reexecuting a
program each time a single bug is discovered can be a time-consuming task,
especially on a heavily loaded system.  Often when I discover a program error
while using a symbolic debugger, I will "patch" around the error and
continue the debugging run.  This is usually accomplished simply by
depositing the proper value in some variable.

I've found this technique to be a great timesaver.

					-- Roger Goun

ARPA:    goun%cadlac.DEC@decwrl.ARPA
UUCP:    {allegra, decvax, ihnp4, ucbvax}!decwrl!dec-rhea!dec-cadlac!goun
USPS:    Digital Equipment Corp., APO-1/B4
         100 Minuteman Road; Andover, MA 01810-1098
Tel:     (617) 689-1675