home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.unix.programmer:4412 comp.lang.c:12663 comp.arch:9014
- Newsgroups: comp.unix.programmer,comp.lang.c,comp.arch
- Path: sparky!uunet!uunet.ca!geac!zooid!ross
- From: Ross Ridge <ross@zooid.guild.org>
- Subject: Re: What would you like in a debugger?
- Organization: ZOOiD BBS
- Date: Sat, 22 Aug 1992 19:52:13 GMT
- Message-ID: <1992Aug22.195213.3311@zooid.guild.org>
- References: <1992Aug16.165055.19638@zooid.guild.org> <158@sc.sni.ie>
- Lines: 29
-
- ross@zooid.guild.org (Ross Ridge) writes:
- >Perhaps people are already using their debuggers to trace problems
- >efficiently. Nah... since you can't do that, how could any one else?
-
- bryan@sc.sni.ie writes:
- >In my mind, running out of CPU quota when tracing a variable within dbx
- >does not constitute efficiency.
-
- You can't blame that on the debugger, it's the fault of a) letting
- accountants get to close to your computer, and b) an OS and/or
- hardware architecture that forces dbx to jump through loops to
- trace a variable.
-
- > Maybe we are operating on different interpretations of the word.
-
- A more efficient debugger (in the original context) is one that lets me
- find bugs faster. For most bugs, I can find the problem the fastest
- without any debugger. For a lot of the rest, I find adb it about the
- quickest tool. For something really perplexing I'll use gdb. But the
- only time I've found a more advanced debugger useful (td386) is when I'm
- "reverse-engineering" binaries.
-
- Ross Ridge
-
- --
- Ross Ridge - The Great HTMU l/ //
- [OO][oo]
- ross@zooid.guild.org /()\/()/
- uunet.ca!zooid!ross db //
-