Here's my guess... On PowerPC architectures, virtual memory is broken into segments. Each segment is 256MB large. The code that lays out each processes memory address space probably is probably coded to create one and only one stack segment. You'll probably need to modify something around that mechanism. I'm not sure, but I imagine there could be some weird virtual memory issues regarding cross-segment stack boundaries which would be why this isn't implemented. *shrug* Just another guess. --Steve On Fri, Apr 23, 2004 at 11:04:19AM -0600, Nicolas Bock wrote:

Hello list,

I was trying to raise the stacksize limit of the OS X 10.3.3 kernel by

changing

#define MAXSSIZ (64*1024*1024)

to

#define MAXSSIZ (RLIM_INFINITY)

in the file

xnu-517.3.15/bsd/ppc/vmparam.h

The new kernel reports the hard limit for stacksize to be unlimited as

I had hoped, but I am still not able to raise the actual stacksize

limit to anything beyond 256 MB. Does anyone know what the reason for

that could be? Do I have to change something else?

Thanks, nick

_______________________________________________

darwin-kernel mailing list | darwin-kernel@lists.apple.com

Help/Unsubscribe/Archives:

http://www.lists.apple.com/mailman/listinfo/darwin-kernel

Do not post admin requests to the list. They will be ignored.

_______________________________________________ darwin-kernel mailing list | darwin-kernel@lists.apple.com Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/darwin-kernel Do not post admin requests to the list. They will be ignored.