Greg Haerr writes: > > > : The function stack_check() in arch/i86/kernel/process.c checks to see > : whether the stack pointer is less then the brk pointer, and segfaults if it > : is. > : > stack_check() is used by the kernel to see if the user process > has run out of space, only during a system call. If anyone really cares, > I think that we need to implement the checking on a per-function call basis, > as this is where all stack data is actually allocated, and where the > process actually trashes the stack. > I don't think we can do this without slaying performance, and relying on user programs to look after themselves. Al
- RE: ELKS: Application Code, Data, Heap and Stack Size?? Anonymous
- RE: ELKS: Application Code, Data, Heap and Stack Size?? Anonymous
- RE: ELKS: Application Code, Data, Heap and Stack Size?? Anonymous
- RE: ELKS: Application Code, Data, Heap and Stack Size?? Anonymous
- RE: ELKS: Application Code, Data, Heap and Stack Size?? Anonymous
- RE: ELKS: Application Code, Data, Heap and Stack Size?? Anonymous
- RE: ELKS: Application Code, Data, Heap and Stack Size?? Anonymous
- RE: ELKS: Application Code, Data, Heap and Stack Size?? Anonymous
- RE: ELKS: Application Code, Data, Heap and Stack Size?? Anonymous
- RE: ELKS: Application Code, Data, Heap and Stack Size?? Greg Haerr
