Re: Detailed Stack Information Patch [2/3]

Mikael Pettersson
2009-04-03T07:33:59Z

Stefani Seibold writes:
> I think a user space daemon will be the a good way if the /proc/*/maps
> or /proc/*/stack will provide the following information:
>
> - start address of the stack
> - current address of the stack pointer
> - highest used address in the stack

You're assuming
1. a thread has exactly one stack
2. the stack is a single unbroken area
3. the kernel knows the location of this area

None of these assumptions are necessarily valid, esp. in
the presence of virtualizers, managed runtimes, or mixed
interpreted/JIT language implementations.