David Laight <david@l8s.co.uk> wrote:

> What happens if you ktrace ps ?

$ ktrace -t+S ps
PID TTY   STAT    TIME COMMAND
110 ttyp0 R+   0:00.00 ps 
764 ttyp0 Ss   0:00.00 -ksh  

The kdump lacks some GIO records, but that can be easily fixed, by
adding the appropriate tracepoints in init_sysctl.c
 
   110      1 ps       CALL  __sysctl(0xbfbfdfb0,5,0,0xbfbfdd7c,0,0)
   110      1 ps       MIB   1.64.110.88.0
   110      1 ps       RET   __sysctl 0
   110      1 ps       CALL  __sysctl(0xbfbfdfb0,5,0x8056000,
0xbfbfdd7c,0,0)
   110      1 ps       MIB   1.64.110.88.6
   110      1 ps       RET   __sysctl 0
   110      1 ps       CALL  __sysctl(0xbfbfdf80,4,0xbfbfdf78,
0xbfbfdf7c,0,0)
   110      1 ps       MIB   1.48.110.2
   110      1 ps       RET   __sysctl 0
   110      1 ps       CALL  break(0x806c000)
   110      1 ps       RET   break 0
   110      1 ps       CALL  __sysctl(0xbfbfdf80,4,0x806b080,
0xbfbfdf7c,0,0)
   110      1 ps       MIB   1.48.110.1
   110      1 ps       RET   __sysctl 0
   110      1 ps       CALL  break(0x806d000)
   110      1 ps       RET   break 0
   110      1 ps       CALL  write(1,0x805b000,0x1b)
   110      1 ps       GIO   fd 1 wrote 27 bytes
       "110 ttyp0 R+   0:00.00 ps 
       "


-- 
Emmanuel Dreyfus
http://hcpnet.free.fr/pubz
manu@netbsd.org