Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!sarah!cs.albany.edu!crdgw1!uakari.primate.wisc.edu!caen!uwm.edu!psuvax1!hsdndev!dartvax!mars!nic!kira!emily!wollman
From: wollman@emily.uvm.edu (Garrett Wollman)
Newsgroups: comp.lang.c
Subject: Re: debugging run-time Unix C programs
Message-ID: <1991May16.190136.7743@uvm.edu>
Date: 16 May 91 19:01:36 GMT
References: <42138@cup.portal.com> <262@bria.UUCP>
Sender: news@uvm.edu
Distribution: usa
Organization: University of Vermont - EMBA Computing Facility
Lines: 23

In article <262@bria.UUCP> uunet!bria!mike writes:
>Well, since all UNIX systems were not created equal, you may or may not have
>access to the three standard ones.  There is adb, which is rather bare-bones
>and cryptic; there is sdb which is bare-bones, cryptic, but provides source
>references; and there is dbx which is a bit nicer (IMHO) than the other two.
>
>Of course, you may have third party debuggers as well as vendor added
>goodies, but these are three that I'm familiar with.

[Not really C-related]

Around here, most people use gdb (the GNU DeBugger), either under
Emacs gdb-mode, or under one of the X-based interfaces; except on
Silcon Graphics boxen, which gdb doesn't support (MIPS processor and
COFF) yet, where everybody uses dbx, and possibly edge, an SGI
front-end for dbx.

-GAWollman

Garrett A. Wollman - wollman@emily.uvm.edu

Disclaimer:  I'm not even sure this represents *my* opinion, never
mind UVM's, EMBA's, EMBA-CF's, or indeed anyone else's.