Re: Is /proc/*/mem broken?

Alan Curry (pacman-kernel@cqc.com)
Fri, 14 May 1999 23:09:17 -0500 (EST)

Pauline Middelink writes the following:
>
>LS,
>
>Well, the subject says it all. I just discovered that on my
>2.2.7 and 2.2.8 machines /proc/1/mem no longer gives meaningfull
>information:
>
> cat: /proc/5703/mem: No such process

You have to be ptrace attached to the process before you can read its mem.
PID 1 is not ptrace'able, so /proc/1/mem not very useful at all. Perhaps you
were thinking of /proc/pid/maps?

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/