Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!julius.cs.uiuc.edu!coolidge
From: coolidge@cs.uiuc.edu (John Coolidge)
Newsgroups: comp.unix.aux
Subject: Re: sdb: the debugger from hell...
Message-ID: <1990Dec14.054041.1695@julius.cs.uiuc.edu>
Date: 14 Dec 90 05:40:41 GMT
References: <27409.27657285@kuhub.cc.ukans.edu> <1990Dec12.170349.5851@servalan.uucp>
Sender: news@julius.cs.uiuc.edu (USENet News)
Reply-To: coolidge@cs.uiuc.edu
Organization: U of Illinois, Dept. of Computer Science, Systems Research Group
Lines: 47

rmtodd@servalan.uucp (Richard Todd) writes:
>brownrigg@kuhub.cc.ukans.edu writes:
>Yep.  About the only good thing about sdb is that it is more clueful about
>handling C structures et al than its predecessor adb.

adb is still fairly useful if you want to quick-and-dirty look at
a bunch of assembly, though :-) (actually, this is often something
I want to do; it's useful when doing operating systems development
at times :-)).

>However, there is relief courtesy of your friendly next-door
>(literally) archive site, wuarchive.wustl.edu.  Lurking in the /systems/aux/
>gnu directory are executables for GDB, the GNU Debugger.  It does know from
>typecasts, groks *myPtr, has a conditional trap facility that'll blow your
>mind, and I haven't yet seen it core dump, and it's got a whole lot more 
>nice features, too.  Note that there are two versions of gdb on wuarchive;
>the one starting with "sgdb-..."  is for programs compiled with cc; the one
>starting with "gdb-..." is for programs compiled with gcc (or g++ -- gdb has
>some support for C++ debugging).  

Actually, there are three versions. gdb-3.5 exists in two versions:
the 'gdb' version which reads dbx format debugging symbols (produced
by gcc/g++ and gas) and the 'sgdb' version which reads sdb format
symbols (cc/as). gdb-3.6- exists only in the dbx format; I'm unsure
as to whether supporting sdb format symbols is a useful thing to
do (is anyone out there actually using sgdb? Or any of the compilers
that produce sdb format symbols?).

I advise using gdb-3.6-, since it does a much better job of handling
g++ and also doesn't coredump on files using shared libraries (and
in general just seems more robust). It is pretest software, though;
you should delete it in favor of 3.6 when the full release comes out
(in fact, there seems to be some doubt about 3.6; some people have
told me that they may go straight to 4.0).

I'll be off the net for at least one and perhaps three weeks (vacation;
hope to have network access in a week).

Happy holidays!

--John

--------------------------------------------------------------------------
John L. Coolidge     Internet:coolidge@cs.uiuc.edu   UUCP:uiucdcs!coolidge
Of course I don't speak for the U of I (or anyone else except myself)
Copyright 1990 John L. Coolidge. Copying allowed if (and only if) attributed.
You may redistribute this article if and only if your recipients may as well.