Staging
v0.5.1
v0.5.1
https://github.com/python/cpython
Revision 20cc6be1aada880f0267eaca39ebb70d0e790692 authored by Andrew M. Kuchling on 05 October 2006, 19:32:52 UTC, committed by Andrew M. Kuchling on 05 October 2006, 19:32:52 UTC
you find that Python does print "MemoryError". There's no traceback and no indication of which line of code is responsible, but it's better than a segfault.] Handle NULL nodes while parsing. I'm not entirely sure this is correct. There might be something else that needs to be done to setup the error. Klocwork #295.
1 parent 6d0bc3e
Tip revision: 20cc6be1aada880f0267eaca39ebb70d0e790692 authored by Andrew M. Kuchling on 05 October 2006, 19:32:52 UTC
[Backport r51222 | neal.norwitz -- if you hack the code to set r=NULL,
[Backport r51222 | neal.norwitz -- if you hack the code to set r=NULL,
Tip revision: 20cc6be
File | Mode | Size |
---|---|---|
RPM | ||
ACKS | -rw-r--r-- | 9.6 KB |
AIX-NOTES | -rw-r--r-- | 8.0 KB |
BeOS-NOTES | -rw-r--r-- | 1.4 KB |
BeOS-setup.py | -rw-r--r-- | 23.2 KB |
HISTORY | -rw-r--r-- | 375.2 KB |
NEWS | -rw-r--r-- | 243.2 KB |
NEWS.help | -rw-r--r-- | 2.5 KB |
PURIFY.README | -rw-r--r-- | 3.6 KB |
Porting | -rw-r--r-- | 1.9 KB |
README | -rw-r--r-- | 1.4 KB |
README.valgrind | -rw-r--r-- | 3.3 KB |
RFD | -rw-r--r-- | 3.9 KB |
SpecialBuilds.txt | -rw-r--r-- | 11.6 KB |
build.sh | -rwxr-xr-x | 6.2 KB |
cheatsheet | -rw-r--r-- | 103.9 KB |
find_recursionlimit.py | -rw-r--r-- | 2.2 KB |
gdbinit | -rw-r--r-- | 2.8 KB |
indent.pro | -rw-r--r-- | 66 bytes |
pymemcompat.h | -rw-r--r-- | 3.1 KB |
python-mode.el | -rw-r--r-- | 138.6 KB |
python.man | -rw-r--r-- | 11.9 KB |
setuid-prog.c | -rw-r--r-- | 5.3 KB |
valgrind-python.supp | -rw-r--r-- | 3.6 KB |
vgrindefs | -rw-r--r-- | 505 bytes |
vimrc | -rw-r--r-- | 3.2 KB |
![swh spinner](/static/img/swh-spinner.gif)
Computing file changes ...