5:08:15White_Flameon control stack exhaustion, it says "PROCEED WITH CAUTION". What are the cautions to take?
5:08:53White_FlameDoes it have to do with unwinding, or potential trampling of important info after the stack, or what sorts of danger?
5:09:22White_FlameI would like to programmatically recover from such situations, substituting in a slower version with less stack pressure if such is hit
5:10:14White_Flameto my understanding, it doesn't appear that threads can be created with different stack sizes, which would be ideal
7:34:10flip214White_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
7:34:16flip214might be good to have upstream as well
7:34:32flip214or just a (max ...) instead of (or ...)
7:43:59White_Flameyou mean src/runtime/thread.c ? I'm not seeing those vars in the lisp side
7:58:23flip214right there. yeah, I hoped to be able to modify from lisp as well.
8:02:28White_Flamein any case, my primary question was about the "proceed with caution" and what problems might step from the stack overflow
8:03:03White_Flamein terms of preventing issues, and restarting the task