home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.arch
- Path: sparky!uunet!psinntp!ficc!peter
- From: peter@ferranti.com (peter da silva)
- Subject: Re: Why would you like a debugger (Was: What would you like in a debugger?
- Message-ID: <id.BVDS.EPB@ferranti.com>
- Reply-To: peter@ferranti.com (Peter da Silva)
- Organization: Xenix Support, FICC
- References: <19920809.175600.935@almaden.ibm.com> <343@moene.indiv.nluug.nl> <id.8J9S.1P4@ferranti.com> <1992Aug13.144226.8391@yrloc.ipsa.reuter.COM>
- Date: Sat, 15 Aug 1992 19:32:50 GMT
- Lines: 15
-
- In article <1992Aug13.144226.8391@yrloc.ipsa.reuter.COM> rbe@yrloc.ipsa.reuter.COM (Robert Bernecky) writes:
- > Ah, perhaps I'm missing something here, but I personally do NOT like
- > the idea of modifying ANY code in order to debug it. That is, insertion
- > of printfs is harmful to maintainability.
-
- It can be. I've had my share of heisenbugs. But I've had about as many "cured"
- by running them under the debugger, or by linking with a debugging version of
- malloc. A good interpreter/compiler would allow you to make changes in a local
- copy, avoiding the telephone problem. Plus, if you use a "DEBUG_PRINTF" macro
- they're easy to find...
- --
- Peter da Silva `-_-'
- $ EDIT/TECO LOVE 'U`
- %TECO-W-OLDJOKE Not war? Have you hugged your wolf today?
- Ferranti Intl. Ctls. Corp. Sugar Land, TX 77487-5012 +1 713 274 5180
-