Stack size limits
Stack size limits
- Subject: Stack size limits
- From: Volker Blum <email@hidden>
- Date: Tue, 11 Jul 2017 15:18:02 +0200
Dear all,
Here is an interesting issue that I have been unable to figure out. It concerns
the behavior of xterm vs the native Mac OS terminal.
I have a system running Sierra, 10.12.5, and XQuartz 2.7.11 (xorg-server
1.18.4) . All this seems to be current.
When I open a new xterm, and say ulimit -a, I get:
core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
file size (blocks, -f) unlimited
max locked memory (kbytes, -l) unlimited
max memory size (kbytes, -m) unlimited
open files (-n) 4864
pipe size (512 bytes, -p) 1
stack size (kbytes, -s) 512
cpu time (seconds, -t) unlimited
max user processes (-u) 709
virtual memory (kbytes, -v) unlimited
A stack size of 512 kB is too low for anything I do. Unfortunately, ulimit -s
50000 (or any other value) is not permitted.
I first put this down to a limitation of Mac OS and was unable to discern a
solution.
However, I recently noticed that the native terminal on Mac OS behaves
differently. I am allowed to change the he stack size if I do this first thing
after opening the terminal.
The question is: Is this behavior known? What I would really like to do is
change the stack size on xterm. Does anyone know what might prevent me from
doing that?
Thank you,
Best wishes
VB
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden