Charles> I get the exact same value. Of course the amount of other
Charles> stuff running makes no differemce, you get the core dump
Charles> because you've hit the RLIMIT for stack usage, not because
Charles> you've exhausted memory. Amount of RAM in the machine, or swap
Charles> space in use has nothing to do with it. Do "ulimit -s
Charles> unlimited" and see what happens...
Makes no difference:
% ./python
Python 2.0b1 (#81, Aug 31 2000, 15:53:42) [GCC 2.95.3 19991030 (prerelease)] on linux2
Copyright 1991-1995 Stichting Mathematisch Centrum, Amsterdam
Copyright 1995-2000 Corporation for National Research Initiatives (CNRI)
>>>
% ulimit -a
core file size (blocks) 0
data seg size (kbytes) unlimited
file size (blocks) unlimited
max locked memory (kbytes) unlimited
max memory size (kbytes) unlimited
open files 1024
pipe size (512 bytes) 8
stack size (kbytes) unlimited
cpu time (seconds) unlimited
max user processes 2048
virtual memory (kbytes) unlimited
% ./python Misc/find_recursionlimit.py
...
Limit of 2300 is fine
recurse
add
repr
init
getattr
getitem
Limit of 2400 is fine
recurse
add
repr
Segmentation fault
Skip
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4