Path: utzoo!utgpu!water!watmath!clyde!cbosgd!ucbvax!ucbcad!pasteur!ames!umd5!decuac!felix!zemon
From: hubcap@hubcap.clemson.edu (Mike Marshall)
Newsgroups: comp.unix.ultrix
Subject: adb
Message-ID: <19250@felix.UUCP>
Date: 21 Jan 88 21:09:45 GMT
Sender: zemon@felix.UUCP
Reply-To: hubcap@hubcap.clemson.edu (Mike Marshall)
Organization: Clemson University, Clemson, SC
Lines: 38
Approved: zemon@felix.UUCP
Reply-Path:

Everyone knows that with adb you can find out tons of information about
a running system. For example, if you type:

$ adb -k /vmunix /dev/mem

on my system (a 780 running ULTRIX 2.0), and then give the following 
adb command:

swdevt/X

you can list out the swap devices that are mounted.

_swdevt:
_swdevt:	901       ; 9=>uda device   01=>b partition disk 0
_swdevt+4:	1         ; 0=>not mounted, 1=>mounted
_swdevt+8:	82a0      ; physical sectors allotted for swap device.
_swdevt+c:	90e       ; 9=>uda device   0e=>g partition of disk 1
_swdevt+10:	1         ; mounted
_swdevt+14:	140a0     ; physical sectors allotted for swap device.
_swdevt+18:	0        )
_swdevt+1c:	0        >  three 0's mark the end of the swap device.
_swdevt+20:	0        )


Unfortunately, the only reason I knew how to comment the above output, is
because someone held my hand through it, and told me what each line meant.

What if I wanted to know how to interpret the info at another offset (ttwrite
for example)... the only way I can imagine ever being able to know what
the *!$%##!! adb is telling me about ttywrite is to buy source and spend
9 months staying up all night studying it.

Is that really the only way to ever figure out what is going on, or am
I missing something?

Thanks...

-Mike Marshall    hubcap@hubcap.clemson.edu     ...!hubcap!hubcap