thanks for the posting. i think it would be helpful if you also posted a few more words on the problems that raising the segment limit does solve, and additional problems that it could solve. and discuss the pros and cons of the new system.
as an example, > I finally changed libthread. Currently, libthread allocates thread stacks > via malloc()/free(). I converted libthread to allocate thread stacks via > segattach() - each thread stack consists of three segments, an anonymous > segment flanked by two SG_NONE redzones. the point, of course, is to catch thread library programs that use more stack than they've asked for. typically, accessing memory above the stack is not a problem, so a single red zone below the stack is enough. this red zone need not be an actual segment, if the thread library picks segment addresses. although this would force the thread library to keep tabs on the top of the heap. - erik
