[Ecls-list] [Maxima] segmentation fault with Maxima/ECL

[Robert Dodier]

On Thu, Sep 25, 2008 at 12:38 PM, Juan Jose Garcia-Ripoll
<juanjose.garciaripoll at googlemail.com> wrote:

> I have been tracking this issue further on different machines. On
> those which have large enough C stacks, there is a binding stack
> overflow due to the many special variables that are bound through
> different function calls. I have already implemented but not uploaded
> code to create restartable conditions that grow the stack on demand.
> This works for all functions I have defined, but still breaks with
> Maxima because Maxima ignores the condition and, furthermore, prevents
> the debugger and the stack growth code from being executed. Hence, the
> only sensible solution for you will be to use the new routines to
> enlarge the binding and frame stacks _before_ executing Maxima.

OK, this sounds interesting. Please let us know when that
code is committed.

> As I said, the binding and frame stacks are now checked (not yet
> uploaded) and can grow. The C stack... I do not have enough low level
> knowledge to hack the system calls which might enlarge the stack.

>From my point of view, it would be enough to at least detect a stack
overflow, so that a Lisp error can be triggered, instead of having the
process die with a segfault.

Robert Dodier