"Lisp stack overflow" in Common Lisp.

zaxonus · 12-17-2023, 02:38 AM

Hi!

I get this error message when running a lisp program that I have used many times before, with no problem:

*** - Lisp stack overflow. RESET

What could be the issue ?
And what would be a good way to tackle the problem ?

slac-in-the-box · 12-17-2023, 04:36 AM

Run the source in a repl, and see what lisp has to say about it.

NevemTeve · 12-17-2023, 05:36 AM

You might have added infinite recoursion lately. Or simply the `ulimit -d` value is different?

zaxonus · 12-17-2023, 09:31 AM

@NevemTeve. How can I know the value of 'ulimit -d' ?
And how can I change it ? If it has changed, it was not on my will.
About adding infinite recursion lately, it's hard to think so because this same code has bee used before and never showed any issue.

sundialsvcs · 12-17-2023, 11:30 AM

If the program is "suddenly malfunctioning," then something(!) has "changed."

This is a great argument for setting up each project directory as a "git repository," and using it for version control. The git init command creates a hidden ".git" directory within the project folder, and, "there's your repository." (No "server" required.)

"git" is available for every operating system, and it works the same way.

Each time anyone makes a change to the contents, they use git commit and explain why. You can also now authoritatively determine exactly what, if anything, "has changed." And exactly what the change was. You can git revert any particular change if you change your mind ... and even "revert the revert" if you change your mind again.

Otherwise, you have no real way to know.

NevemTeve · 12-18-2023, 12:14 AM

@OP Just enter this command in your shell:

Code:

$ ulimit -a
core file size          (blocks, -c) 0
data seg size           (kbytes, -d) unlimited
scheduling priority             (-e) 0
file size               (blocks, -f) unlimited
pending signals                 (-i) 31801
max locked memory       (kbytes, -l) 64
max memory size         (kbytes, -m) unlimited
open files                      (-n) 1024
pipe size            (512 bytes, -p) 8
POSIX message queues     (bytes, -q) 819200
real-time priority              (-r) 0
stack size              (kbytes, -s) 8192
cpu time               (seconds, -t) unlimited
max user processes              (-u) 4096
virtual memory          (kbytes, -v) unlimited
file locks                      (-x) unlimited