Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!ames!sgi!arisia!quintus!ok
From: ok@quintus.uucp (Richard A. O'Keefe)
Newsgroups: comp.sys.apollo
Subject: Re: adb missing ...
Keywords: adb, dbx machine level facilities
Message-ID: <342@quintus.UUCP>
Date: 2 Sep 88 05:56:13 GMT
References: <8808291425.AA04608@richter.mit.edu> <3e3043cd.12edf@apollo.COM> <15687@shemp.CS.UCLA.EDU>
Sender: news@quintus.UUCP
Reply-To: ok@quintus.UUCP (Richard A. O'Keefe)
Organization: Quintus Computer Systems, Inc.
Lines: 19

In article <15687@shemp.CS.UCLA.EDU> casey@cs.ucla.edu (Casey Leedom) writes:
>  Except that dbx's machine level facilities are pathetic.  When I try to
>display a chunk of code it says "program is not active".  I have to start
>the friggin' program just to look at it!  When I finally do get it
>started and start looking at things, it prints everything out via it's
>absolute address instead of a symbol plus an offset.  And, in fact, it
>never seem to print anything symbolically.

This is not true of all versions of dbx.  For example, I just did
	% dbx payste		# payste is a program of mine
	(dbx) &main+0x1a/3i	# print 3 instrs starting at "main"+1a
and it printed
	main+0x1a:              tstl    d0
	main+0x1c:              beqs    main+0x68
	main+0x1e:              pea     a6@(-0xf0)

Mind you, this was SunOS 3.2 on a Sun-3/50, but exactly the features
are described in the ULTRIX manual page for dbx.  Is the Apollo one
different?