Changes by Terry J. Reedy tjre...@udel.edu:
--
resolution: - out of date
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9812
___
On Wed, Sep 8, 2010 at 6:55 PM, Paul Rubin no.em...@nospam.invalid wrote:
Carl Banks pavlovevide...@gmail.com writes:
Since Python 2.7 is released, Python 2.5 is no longer accepting bug
fixes, only security fixes. So be aware.
Segfaults should be treated as security holes unless there's
: test_cpickle.nested_dicts_in_threaded_env.diff
keywords: patch
messages: 115950
nosy: kdombrowski
priority: normal
severity: normal
status: open
title: cPickle segfault with nested dicts in threaded env
type: crash
versions: Python 2.5
Added file:
http://bugs.python.org/file18812/test_cpickle.nested_dicts_in_threaded_env.diff
Amaury Forgeot d'Arc amaur...@gmail.com added the comment:
Python has several known crashers, they are not considered as security holes.
It seems that FreeBSD has a small stack size for threads (64k); did you try to
increase it with thread.stack_size(10**6)?
--
nosy:
Hi all,
Before creating an issue @ bugs.python.org I wanted to run the
following by everyone
We are having a difficult time with what looks like a cPickle issue
when given a data structure containing 15 nested dictionaries, but
only when threading is involved
Environment is FreeBSD 8, Python
On Wednesday 08 September 2010, it occurred to Kenneth Dombrowski to exclaim:
Environment is FreeBSD 8, Python 2.5.5
Which architecture?
Also, Python 2.5 is frightfully old. There's not really any problem with still
using it, but nobody's maintaining it upstream, so don't bother reporting a
On Sep 8, 11:58 am, Kenneth Dombrowski kdombrow...@gmail.com wrote:
Hi all,
Before creating an issue @ bugs.python.org I wanted to run the
following by everyone
We are having a difficult time with what looks like a cPickle issue
when given a data structure containing 15 nested dictionaries,
Carl Banks pavlovevide...@gmail.com writes:
Since Python 2.7 is released, Python 2.5 is no longer accepting bug
fixes, only security fixes. So be aware.
Segfaults should be treated as security holes unless there's convincing
reasons that no exploit is possible. So the bug should be reported
In article mailman.583.1283975836.29448.python-l...@python.org,
Thomas Jollans tho...@jollybox.de wrote:
Also, Python 2.5 is frightfully old. [...]
Frightfully??? I'm sure plenty of people are still using Python 2.3
in production environments (certainly my last job did as of 1.5 years
ago,
