Changes by Terry J. Reedy tjre...@udel.edu:
--
resolution: - fixed
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue3338
___
Changes by Daniel Diniz aja...@gmail.com:
--
dependencies: +test_cpickle crash on AMD64 Windows build
priority: - normal
versions: +Python 2.6 -Python 2.4
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue3338
Antoine Pitrou pit...@free.fr added the comment:
Now that #3640 has been fixed, this bug is probably fixed too (at least
in trunk and py3k).
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue3338
Antoine Pitrou [EMAIL PROTECTED] added the comment:
Well, it's definitely a bug, or inconsistency, if you like, between
cPickle and pickle.
There is clearly a problem with cPickle stack consumption and a new bug has been
opened for this in #3640.
What I don't agree with is your argument that
Antoine Pitrou [EMAIL PROTECTED] added the comment:
Well, the standard recursion limit is precisely there to guard against
segfaults when blowing up the C stack, so if you make the recursion
limit much larger, it's quite normal to get segfaults.
Therefore, I don't think this is a real bug.
Darryl Dixon [EMAIL PROTECTED] added the comment:
Well, it's definitely a bug, or inconsistency, if you like, between
cPickle and pickle.
My gut says that probably there is some fault in cPickle that is causing
this. When pickle.py can recurse to 10,000+ and cPickle segfaults at
2600 on a 64bit
Changes by Jesús Cea Avión [EMAIL PROTECTED]:
--
nosy: +jcea
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3338
___
___
Python-bugs-list mailing list
Darryl Dixon [EMAIL PROTECTED] added the comment:
That is a very interesting observation (x4), especially in light of #3373
Unfortunately I don't really have the (p|g)db -foo to debug either of
these properly :(
___
Python tracker [EMAIL PROTECTED]
Darryl Dixon [EMAIL PROTECTED] added the comment:
Hmm, looks like this dup's 2702... Funny how two people find the same
thing within a short window of each other *sighs* so looks like it's
probably fixed. I'll test /trunk against the failing testcase below and
make sure all is OK.
D
Darryl Dixon [EMAIL PROTECTED] added the comment:
No, I've just tested /trunk, including r64595, and the Segmentation
fault is still present, eg:
Python 2.6b1+ (trunk:64998, Jul 16 2008, 15:50:22)
[GCC 4.1.1 20070105 (Red Hat 4.1.1-52)] on linux2
Type help, copyright, credits or license for
Darryl Dixon [EMAIL PROTECTED] added the comment:
Happens with Python 2.5.2 on 64bit also:
Python 2.5.2 (r252:60911, Apr 21 2008, 11:17:30)
[GCC 4.2.3 (Ubuntu 4.2.3-2ubuntu7)] on linux2
Type help, copyright, credits or license for more information.
import platform
platform.architecture()
Martin v. Löwis [EMAIL PROTECTED] added the comment:
Can you try this for a newer version? For 2.4, such problems will not be
fixed anymore.
--
nosy: +loewis
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3338
New submission from Darryl Dixon [EMAIL PROTECTED]:
In at least Python 2.4, using cPickle.Pickler to try and pickle a nested
chain of objects more than about 2590 objects deep causes the Python
interpreter to segfault. This doesn't seem to happen when using the pure
Python pickle module.
It is
13 matches
Mail list logo
