[issue17278] SIGSEGV in _heapqmodule.c

2013-03-04 Thread Antoine Pitrou
Antoine Pitrou added the comment: Ok, committed, thank you! -- resolution: -> fixed stage: patch review -> committed/rejected status: open -> closed ___ Python tracker ___ _

[issue17278] SIGSEGV in _heapqmodule.c

2013-03-04 Thread Roundup Robot
Roundup Robot added the comment: New changeset 905b02749c26 by Antoine Pitrou in branch '3.2': Issue #17278: Fix a crash in heapq.heappush() and heapq.heappop() when the list is being resized concurrently. http://hg.python.org/cpython/rev/905b02749c26 New changeset 451299b97b4f by Antoine Pitro

[issue17278] SIGSEGV in _heapqmodule.c

2013-03-04 Thread Roundup Robot
Roundup Robot added the comment: New changeset 21ded74b51fa by Antoine Pitrou in branch '2.7': Issue #17278: Fix a crash in heapq.heappush() and heapq.heappop() when the list is being resized concurrently. http://hg.python.org/cpython/rev/21ded74b51fa -- nosy: +python-dev _

[issue17278] SIGSEGV in _heapqmodule.c

2013-03-04 Thread Raymond Hettinger
Raymond Hettinger added the comment: Antoine, thanks for the patch. This looks like a reasonable solution that is fast and prevents segfaults. -- assignee: rhettinger -> pitrou ___ Python tracker

[issue17278] SIGSEGV in _heapqmodule.c

2013-03-04 Thread Raymond Hettinger
Changes by Raymond Hettinger : -- Removed message: http://bugs.python.org/msg183401 ___ Python tracker ___ ___ Python-bugs-list mailin

[issue17278] SIGSEGV in _heapqmodule.c

2013-03-03 Thread Raymond Hettinger
Raymond Hettinger added the comment: Antoine, thanks for the patch. This looks like a reasonable solution that is fast and prevents segfaults. The error message should say more than just that the size changed. it should also note that the heap may no longer be in the heap condition since it w

[issue17278] SIGSEGV in _heapqmodule.c

2013-02-26 Thread Raymond Hettinger
Changes by Raymond Hettinger : -- assignee: -> rhettinger priority: normal -> high ___ Python tracker ___ ___ Python-bugs-list mailin

[issue17278] SIGSEGV in _heapqmodule.c

2013-02-23 Thread Antoine Pitrou
Antoine Pitrou added the comment: Updated patch with tests. -- stage: -> patch review Added file: http://bugs.python.org/file29212/heapq_race2.patch ___ Python tracker ___ _

[issue17278] SIGSEGV in _heapqmodule.c

2013-02-23 Thread Antoine Pitrou
Antoine Pitrou added the comment: And a patch (for 2.7). -- keywords: +patch versions: +Python 3.2, Python 3.3, Python 3.4 Added file: http://bugs.python.org/file29211/heapq_race.patch ___ Python tracker __

[issue17278] SIGSEGV in _heapqmodule.c

2013-02-23 Thread Antoine Pitrou
Antoine Pitrou added the comment: Here is a reproducer. -- nosy: +pitrou Added file: http://bugs.python.org/file29210/stressheapq.py ___ Python tracker ___ __

[issue17278] SIGSEGV in _heapqmodule.c

2013-02-22 Thread Charles-François Natali
Charles-François Natali added the comment: The heapq C implementation is apparently not thread-safe: PyObject_RichCompareBool() and Py_DECREF() can lead to arbitrary python code being called, which can result in a context switch. -- nosy: +neologix

[issue17278] SIGSEGV in _heapqmodule.c

2013-02-22 Thread Serhiy Storchaka
Changes by Serhiy Storchaka : -- components: +Extension Modules -Library (Lib) nosy: +rhettinger, stutzbach ___ Python tracker ___ ___

[issue17278] SIGSEGV in _heapqmodule.c

2013-02-22 Thread maxxedev
New submission from maxxedev: I've been getting sporadic SIGSEGV crashes in _heapqmodule.c I have not be able to reliably reproduce it, but here is a stacktrace: Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x2d51d940 (LWP 13976)] (gdb) where #0 0x2b617