> There is only one way when the kernel knows and can > inspect the > environment: during evecve.
Alright. Appears to be simply placing ptrs on the userstack, as an array, using the stk_putptr() method (based on sulword store). I can try to do that in reverse. > After execve, the process is at liberty to change the > memory where the > environment was copied. So it _can_ be somewhere else? _Will_ be somewhere else? Since 'u_envp' is not-NULL, I would assume it still points to something valid, since the user process 'probably' would not go 'that low' in the stack during normal situations? Since /proc (as "ps") can pull out the environment from processes, I would assume it exists somewhere, and I can get at it. -- This message posted from opensolaris.org _______________________________________________ opensolaris-code mailing list opensolaris-code@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
