From: Paul Stoeber <paul.stoeber@stud.tu-ilmenau.de>
Subject: segfault after changing max-lisp-eval-depth and max-specpdl-size
Date: Mon, 27 May 2002 17:53:52 +0200 [thread overview]
Message-ID: <20020527155352.GA454374@bruegel.RZ.TU-Ilmenau.DE> (raw)
In GNU Emacs 21.2.1 (powerpc-unknown-linux-gnu)
of 2002-05-26 on xyz
configured using `configure --prefix=/e --without-x'
Important settings:
value of $LC_ALL: nil
value of $LC_COLLATE: nil
value of $LC_CTYPE: nil
value of $LC_MESSAGES: nil
value of $LC_MONETARY: nil
value of $LC_NUMERIC: nil
value of $LC_TIME: nil
value of $LANG: C
locale-coding-system: nil
default-enable-multibyte-characters: t
Built without modification from
MD5:f4b58e5c2d923fc92495e0c2f167c5db URL:ftp://ftp.cs.tu-berlin.de/pub/gnu/emacs/emacs-21.2.tar.gz
I have this expression in my `*scratch*' buffer:
(progn
(setq max-lisp-eval-depth 30000)
(setq max-specpdl-size 30000)
(defun seq (a b)
"Return sequence of integers A, A+1, ..., B as a list."
(if (> a b)
()
(cons a (seq (1+ a) b))))
(length (seq 1 10000)))
I go to its last line and type C-e C-x C-e, and then it looks like this:
(length (seq 1 10000)))Segmentation fault
q@xyz~$
The descriptions of `max-lisp-eval-depth' and `max-specpdl-size'
both say "You can customize this variable."
I have not found this problem in etc/PROBLEMS or info/efaq* .
I think it should be possible to put your functional programmer's hat on
by saying
(setq max-lisp-eval-depth (setq max-specpdl-size 134217727))
or better still
(setq have-lisp-limits nil) ; don't bother me
---
Avoid arbitrary limits on the length or number of _any_ data structure [...]
-- GNU Coding Standards
next reply other threads:[~2002-05-27 15:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-27 15:53 Paul Stoeber [this message]
2002-05-28 20:23 ` segfault after changing max-lisp-eval-depth and max-specpdl-size Richard Stallman
2002-05-28 21:22 ` Paul Stoeber
2002-05-30 17:05 ` Richard Stallman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020527155352.GA454374@bruegel.RZ.TU-Ilmenau.DE \
--to=paul.stoeber@stud.tu-ilmenau.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).