freenode/#sbcl - IRC Chatlog
Search
5:08:15
White_Flame
on control stack exhaustion, it says "PROCEED WITH CAUTION". What are the cautions to take?
5:08:53
White_Flame
Does it have to do with unwinding, or potential trampling of important info after the stack, or what sorts of danger?
5:09:22
White_Flame
I would like to programmatically recover from such situations, substituting in a slower version with less stack pressure if such is hit
5:10:14
White_Flame
to my understanding, it doesn't appear that threads can be created with different stack sizes, which would be ideal
7:34:10
flip214
White_Flame: src/code/target-thread.lisp already uses pthread_attr_setstacksize, using sb-unix::pthread-min-stack ... you could either change that to (or *required-thread-stack-size sb-unix::pthread-min-stack) and override that where needed
8:02:28
White_Flame
in any case, my primary question was about the "proceed with caution" and what problems might step from the stack overflow