Path: utzoo!attcan!uunet!cs.utexas.edu!usc!apple!rutgers!mcnc!duke!macbeth!pusateri
From: pusateri@macbeth.cs.duke.edu (Thomas J. Pusateri)
Newsgroups: comp.sys.att
Subject: Re: 3B1's wsdb (windowing sdb); does it function?
Summary: try gdb and gnu emacs
Message-ID: <20593@duke.cs.duke.edu>
Date: 3 Jul 90 14:22:53 GMT
References: <31310@cup.portal.com> <1990Jul3.050630.8709@cbnewse.att.com>
Sender: news@duke.cs.duke.edu
Reply-To: pusateri@macbeth.cs.duke.edu (Thomas J. Pusateri)
Organization: Duke University CS Dept.; Durham, NC
Lines: 20

In article <1990Jul3.050630.8709@cbnewse.att.com> gmark@cbnewse.att.com (gilbert.m.stewart) writes:
>In article <31310@cup.portal.com>, thad@cup.portal.com (Thad P Floryan) writes:
>> Has anyone gotten the "wsdb" (from WSDB+IN (from the STORE or osu-cis)) to

I tried wsdb after grabbing it from the STORE. I was not impressed. It is
basically just sdb in a resizable window. I am a vi user but the best
debugging environment around for the unix-pc is running gdb 3.5 from within
gnu emacs. Of course gdb (available from the osu-cis archives already
compiled) runs just fine without gnu emacs, but the pair together is really
nice. This little arrow follows your source code in one window as you step
through it in gdb. I know its alot of work getting gnu emacs running just for
a good debugger, but in my opinion, its well worth it.

I'm not a total convert to gnu emacs but it has some real advantages in
this case.

Tom Pusateri

pusateri@nbsr.duke.edu
pusateri@macbeth.cs.duke.edu