[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Segmentation fault for large values of max-lisp-eval-depth
From: |
Eli Zaretskii |
Subject: |
Re: Segmentation fault for large values of max-lisp-eval-depth |
Date: |
Wed, 28 Apr 2004 20:59:44 +0200 |
> From: Jesper Harder <address@hidden>
> Date: Wed, 28 Apr 2004 14:29:37 +0200
>
> > But the first question is IMHO whether this is indeed the case here.
> > That is, can you check that the stack is overrun in your case?
>
> How do I check that?
Assuming this is an Intel processor, print the value of the ESP
register, and compare that with the stack limit. (For other
processors, you will need to find out which register holds the current
top of the stack.)
The stack limit is stored in a global variable whose name is specific
to the C library used to link Emacs. I don't know the name of that
variable for your library, but asking some guru for your OS would
probably produce the answer.
- Segmentation fault for large values of max-lisp-eval-depth, Jesper Harder, 2004/04/26
- Re: Segmentation fault for large values of max-lisp-eval-depth, Richard Stallman, 2004/04/27
- Re: Segmentation fault for large values of max-lisp-eval-depth, Jesper Harder, 2004/04/27
- Re: Segmentation fault for large values of max-lisp-eval-depth, Eli Zaretskii, 2004/04/28
- Re: Segmentation fault for large values of max-lisp-eval-depth, Jesper Harder, 2004/04/28
- Re: Segmentation fault for large values of max-lisp-eval-depth,
Eli Zaretskii <=
- Re: Segmentation fault for large values of max-lisp-eval-depth, Jesper Harder, 2004/04/28
- Re: Segmentation fault for large values of max-lisp-eval-depth, Eli Zaretskii, 2004/04/29
- Re: Segmentation fault for large values of max-lisp-eval-depth, Jesper Harder, 2004/04/29
- Re: Segmentation fault for large values of max-lisp-eval-depth, Stefan Monnier, 2004/04/29
- Re: Segmentation fault for large values of max-lisp-eval-depth, Richard Stallman, 2004/04/29