Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: Notesfiles $Revision: 1.7.0.10 $; site ccvaxa
Path: utzoo!watmath!clyde!cbosgd!ihnp4!inuxc!pur-ee!uiucdcs!ccvaxa!feldman
From: feldman@ccvaxa.UUCP
Newsgroups: net.unix-wizards
Subject: Re: I HATE DBX! I HATE DBX!
Message-ID: <2000037@ccvaxa>
Date: Fri, 21-Mar-86 06:50:00 EST
Article-I.D.: ccvaxa.2000037
Posted: Fri Mar 21 06:50:00 1986
Date-Received: Sat, 22-Mar-86 22:50:26 EST
References: <4473@think.ARPA>
Lines: 26
Nf-ID: #R:think.ARPA:4473:ccvaxa:2000037:000:1323
Nf-From: ccvaxa.UUCP!feldman    Mar 21 05:50:00 1986



There are at least 3 VAX versions of dbx that I've seen: 4.2, a net.sources
update to 4.2, and 4.3 beta.  The 4.3 beta version is a cut above the others
because it introduces real macros, not just keyword substitutions.  In part
this allows the user to overcome the most frustrating thing about dbx,
namely the amount of typing necessary to do anything.  Of course, it takes
some forethought and experiance to set up useful macros, and they differ
from task to task, but for a drawn out development cycle, I found that it
is a great improvement over the earlier versions.

I'm still disappointed that <CR> doesn't work as in adb.  At least '.' works.

For large debugees, the size of the symbol table is an annoyance.  I've found
that compiling just those files that are in doubt or under development with
-g, and linking -g cuts the symbol table overhead a lot.  You need to be aware
that continuing or stepping such that control returns out into code without
the -g symbols will cause dbx to lose its grip.  But "stop in" someplace that
has debugging symbols will usually be enough to get the job done.

It would be nice if the rest of the world could benefit from Sun's work on their
compilers that cuts the redundancy in the symbol table caused by common include
files.

Mike Feldman
Gould Computer Systems, Urbana IL