Re: stack overflow => segfault in MT

[Vladimir T. <vtz...@gm...>]

On 3/6/11, Don Cohen <don...@is...> wrote:
> I send this on the theory that any segfault qualifies as a clisp bug.
> This is with current source.  On non-MT I get
>   *** - Program stack overflow. RESET
> whereas in MT I get segfault.

With MT - only the "main thread" (first one) has stack overflow detection.
Stack overflow detection/recovery is implemented via libsigsegv and it
supports single stack range.
May be libsigesgv should be enhanced with multiple stack range support? gSam?