Path: utzoo!attcan!uunet!samsung!umich!dgsi!brian
From: brian@cimage.com (Brian Kelley)
Newsgroups: comp.unix.ultrix
Subject: Re: ultrix 4.0 dbx
Message-ID: <1991Jan13.204300.20332@cimage.com>
Date: 13 Jan 91 20:43:00 GMT
References: <10166@pasteur.Berkeley.EDU>
Reply-To: brian@dgsi.UUCP (Brian Kelley)
Organization: Cimage Corp, Ann Arbor, MI
Lines: 23

In article <10166@pasteur.Berkeley.EDU> mao@postgres.Berkeley.EDU (Mike Olson) writes:
>this is new to 4.0; on all our other platforms, and under earlier releases
>of ultrix, dbx doesn't barf like this.  my forlorn question:  does anyone
>have a workaround?  is there any way i can tell dbx to ignore this problem,
>and just not print strings with bad addresses?  this is a major pain.

I agree.  The new dbx is a pain.  It also doesn't work with xdbx (that and
the lousy DEC keryboard means that our programmers would rather use Suns.
(are you listening DEC marketing/sales?)).  I wish DEC had left the old
version intact.  Change a standard tool in several very incompatible ways
(and break it in several ways) and not leave the old version around.  Real
Smart.

We do not have any pre 4.0 hosts at our site.  Has anyone tried using
a version of dbx from a 3.X release under 4.0?

What will OSF/1 be shipping as their debugger?

>					mao@postgres.berkeley.edu


---
brian@cimage.com