home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.programming:2304 comp.unix.programmer:4291 comp.lang.c:12307 comp.arch:8898
- Path: sparky!uunet!idacrd!desj@ccr-p.ida.org
- From: desj@ccr-p.ida.org (David desJardins)
- Newsgroups: comp.programming,comp.unix.programmer,comp.lang.c,comp.arch
- Subject: Re: What would you like in a debugger?
- Message-ID: <1555@idacrd.UUCP>
- Date: 14 Aug 92 01:54:48 GMT
- References: <bosullvn.713038630@unix1.tcd.ie> <1992Aug13.125242.6664@Urmel.Informatik.RWTH-Aachen.DE>
- Sender: desj@idacrd.UUCP
- Organization: IDA Center for Communications Research, Princeton
- Lines: 24
-
- Stephen R. van den Berg <berg@physik.tu-muenchen.de> writes:
- >- The ability to single step in a disassembly window (next to the source
- > window), priceless at the times that you have narrowed down the problem,
- > looked over the code over and over, can't see the bug, suspect a compiler
- > error, and want to make sure.
-
- I'd like to see source-level debugging of assembly language. I don't
- know about other systems, but the Cray Research debugger (cdbx), for
- one, doesn't support this. Note that this isn't at all the same as just
- disassembling the instructions; the debugger should handle
- assembly-language symbols and macros.
-
- Given this, you could hope for something better than what Stephen asked
- for. Given the original source code in a high-level language (say, C),
- and the assembly language output by the compiler, it would be especially
- nice to be able to do source-level debugging on both simultaneously.
- Perhaps the way to do this would be some command for switching between
- the C source and the assembly-language source.
-
- This would also make sense with other forms of interactive code. For
- example, switching between C++ source and the intermediate C code
- produced by cfront.
-
- David desJardins
-