Path: utzoo!attcan!uunet!mcvax!unido!altger!Holgi
From: Holgi@altger.UUCP (Holgi)
Newsgroups: comp.unix.microport
Subject: Re: Interpretation of values reported by nm
Keywords: nm values
Message-ID: <846@altger.UUCP>
Date: 12 Jul 88 14:06:33 GMT
References: <4650@killer.UUCP> <1025@sdcc12.ucsd.EDU>
Reply-To: Holgi@altger.UUCP (Holgi)
Organization: Altos Computer Systems Munich
Lines: 15

In article <1025@sdcc12.ucsd.EDU> mp1@sdcc12.ucsd.EDU (Leroy Dorman) writes:
>In article <4650@killer.UUCP>, richardh@killer.UUCP (Richard Hargrove) writes:
>> I nm /system5, ALL of the addresses, except for u, begin with 0x02.
>> Specifically, proc is 0x0228365a, v is 0x022027ec, etc.
>                          ^^^^
>			  ----  Segment selector
>			      ^^^^
>			      -------  Offset in selector.
>You can't use these directly as offsets into physical memory
>device.

Right, but if you use /dev/kmem (as richardh) you access the kernel virtual
memory (different to /dev/mem) and that works.
I've done it that way and I've got the uid, pid, ppid out of that 'garbage'
but does anyone know the right format to interpret all values ??