Messages in this thread | ![/](/images/icornerl.gif) | | Date | Fri, 25 Apr 2003 16:58:43 -0700 | From | William Lee Irwin III <> | Subject | Re: TASK_UNMAPPED_BASE & stack location |
| |
On Fri, Apr 25, 2003 at 04:52:05PM -0700, badari wrote: > Only problem with moving TASK_UNMAPPED_BASE right above > text would be - limiting the malloc() space. malloc() is clever enough > to mmap() and do the right thing. Once I moved TASK_UNMAPPED_BASE > to 0x10000000 and I could not run some of the programs with large > data segments. > Moving stacks below text would be tricky. pthread library knows > the placement of stack. It uses this to distinguish between > threads and pthreads manager. > I don't know what other librarys/apps depend on this kind of stuff.
STACK_TOP is easy to change to see what goes wrong; it's a single #define in include/asm-i386/a.out.h
Someone should spin it up and see how well pthreads copes.
-- wli - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| ![\](/images/icornerr.gif) |