Re: stack overflow => segfault in MT

Picking up from a thread from 2011 (!!), Vladimir Tzankov wrote:

  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.

With current clisp source I have an example in which non-MT detects a
stack overflow whereas in MT, the main thread, having started no 
other threads, still segfaults.
When I try simple infinite recursions I do get stack overflow
errors that do not exit lisp.

I notice when I trace a function in the recursion, it gets about
twice as deep (41 calls) before segfault in MT as before stack
overflow in non-MT (21 calls).

What would be useful debugging information and how can I get it?


_______________________________________________
clisp-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/clisp-devel