home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!sybus.sybus.com!myrddin!tct!deep6!nifty.UUCP!fgd3
- From: fgd3@nifty.UUCP (Fabbian G. Dufoe, III)
- Newsgroups: comp.sys.amiga.programmer
- Subject: Re: Programming Tools (was: Amiga programmers UNITE)
- Distribution: world
- Message-ID: <fgd3.01p9@nifty.UUCP>
- References: <1992Aug04.235557.26121@NeoSoft.com> <56478@mentor.cc.purdue.edu> <1992Aug10.223432.27395@CS.ORST.EDU> <piet.025y@okapi.sub.org>
- Date: 20 Aug 92 21:08:00 EDT
- Organization: Fabbian G. Dufoe, III
- Lines: 19
-
- In article <piet.025y@okapi.sub.org> piet@okapi.sub.org (Peter Vohmann) writes:
- >Have you ever used CodeProbe (SAS/C debugger)? It does a lot of the things
- >you mentioned (except the guarantee). Yesterday again I stepped through my
- >assembler code with cpr, watching the register values I had done. 'Quit'
- >cleaned everything up nicely, one instruction before the point-of-crash.
- >So what? ;-)
-
- Isn't that a bit of an overstatement? The "Quit" command in CodeProbe
- doesn't clean up everything--CodeProbe doesn't keep track of the resources
- you've allocated. It does get you out of the debugger and let you continue
- what you were doing without a crash. But until you reboot you can't recover
- the memory you've allocated, free any locks that were left hanging, and so
- forth.
-
- --Fabbian G. Dufoe, III
- 350 Ling-A-Mor Terrace South | GEnie: F.DUFOE3
- St. Petersburg, Florida 33705 | internet: fgd3%nifty@tct.com
- 813-823-2350 | uucp: ...tct!deep6!nifty!fgd3
-
-