Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!romp!auschs!awdprime!snap.austin.ibm.com!moody
From: moody@snap.austin.ibm.com
Newsgroups: comp.unix.aix
Subject: Re: Question abt /etc/crash & proc struct
Keywords: crash kernel proc kmem
Message-ID: <8633@awdprime.UUCP>
Date: 20 Jun 91 13:51:59 GMT
References: <1991Jun19.151832.17038@socrates.umd.edu>
Sender: news@awdprime.UUCP
Organization: IBM AWD, Austin
Lines: 41

In article <1991Jun19.151832.17038@socrates.umd.edu> berry@socrates.umd.edu (Joseph Berry     ) writes:
>I cannot access the data structure 'proc' either programmatically or

No one would want user mode programs to have access to this structure.

>from within /etc/crash.  

This can be done if you're looking at a dump.  Use the 'dump' subcommand in crash.  
Various components are listed.  Enter '1' for 'proc'.

The result is a list of ids which may be selected.  They looks something like:

1 0p
2 0u
3 1p
4 1u
....
...

or something like that.  The number of entries depends on the number of processes
running on your machine at the time the dump was taken.

The right column corresponds to a process slot (use the 'proc' subcommand
to see which process slot you may be interested in).  The 'u' and 'p'
suffixes are for 'user area' and 'proc table entry' respectively.
In the above example, by entering 3, I get the proc table entry for
the process in slot 1.  

For a LIVE system, you might look at the getproc, getuser system calls.
See procinfo.h.

>There's something I'm
>missing about accessing addresses in such a high address space. 

You don't have addressibility to the process table memory segment in user mode.


-- 
James Moody				aixnet:moody@moody.austin.ibm.com
Personal Systems Programming Austin	VNET:MOODY@AUSVMQ
AIX Field Support - Level 3		internet:moody@aixwiz.austin.ibm.com