Re: [Sbcl-devel] maximum interrupt nesting depth ?

[Nikodemus S. <nik...@ra...>]

On 1/24/08, Vitaly Mayatskikh <v.m...@gm...> wrote:
> >> fatal error encountered in *SBCL* pid 4768(tid 3085235904):
> >>     *maximum* *interrupt* *nesting* *depth* (32) *exceeded*
> >
> > If a new SBCL doesn't magically fix this, the following bits of information
> > are needed:
>
> I have the same problem using latest sbcl (1.0.13.53) and stumpwm
> window manager: it just falls every 5 sec - 2 min. I've returned
> MAX_INTERRUPTS to its original value and stumpwm runs smoothly now.

Huh, a backtrace would be interesting, but this is probably evidence that
we should be using arrange_return_to_lisp_function for all signal handling.

Cheers,

 -- Nikodemus

>
>
> diff -up ./src/runtime/interrupt.h.orig ./src/runtime/interrupt.h
> --- ./src/runtime/interrupt.h.orig      2008-01-24 14:05:23.000000000 +0100
> +++ ./src/runtime/interrupt.h   2008-01-24 13:08:57.000000000 +0100
> @@ -43,7 +43,7 @@ sigcopyset(sigset_t *new, sigset_t *old)
>   * I've scaled it back (to 256) to see what happens. -- WHN 20000730
>
>   * Nothing happened, so let's creep it back a bit further -- dan 20030411 */
> -#define MAX_INTERRUPTS 32
> +#define MAX_INTERRUPTS 4096
>
>  union interrupt_handler {
>      lispobj lisp;
>
> --
> wbr, Vitaly
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Sbcl-devel mailing list
> Sbc...@li...
> https://lists.sourceforge.net/lists/listinfo/sbcl-devel
>
>