[issue7466] Segmentation fault after about 20 seconds on lenovo T500

flox added the comment: Ok. It is here: http://bugs.python.org/file15520/issue7466.diff -- ___ Python tracker ___ ___ Python-bugs-li

[issue7466] Segmentation fault after about 20 seconds on lenovo T500

Antoine Pitrou added the comment: IMO it would be better to call _PyObject_GC_IS_TRACKED() explicitly rather than rely on a subtle difference between the two APIs as in the current patch. -- ___ Python tracker

[issue7466] Segmentation fault after about 20 seconds on lenovo T500

Changes by flox : Added file: http://bugs.python.org/file15521/issue7466.diff ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscr

[issue7466] Segmentation fault after about 20 seconds on lenovo T500

Changes by flox : Removed file: http://bugs.python.org/file15520/issue7466.diff ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubs

[issue7466] Segmentation fault after about 20 seconds on lenovo T500

flox added the comment: Well... here comes the patch. -- keywords: +patch Added file: http://bugs.python.org/file15520/issue7466.diff ___ Python tracker ___ _

[issue7466] Segmentation fault after about 20 seconds on lenovo T500

Antoine Pitrou added the comment: Ok, you've been faster than me, flox :-) -- ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue7466] Segmentation fault after about 20 seconds on lenovo T500

Antoine Pitrou added the comment: An even simpler way to reproduce: >>> import gc >>> def g(it): ... for x in it: ... gc.collect() ... yield x ... >>> t = tuple(g(range(100))) Erreur de segmentation This is probably caused by the GC optimizations I introduced in trunk and 3.1. ---

[issue7466] Segmentation fault after about 20 seconds on lenovo T500

flox added the comment: Fix is coming soon... ## Sample code: import gc tuple(gc.collect() for i in range(11)) ## python: Objects/tupleobject.c:853: _PyTuple_Resize: ## Assertion `g->gc.gc_refs != (-2)' failed. And Trunk is affected -- versions: +Python 2.7 ___

[issue7466] Segmentation fault after about 20 seconds on lenovo T500

Changes by Antoine Pitrou : -- nosy: +pitrou priority: -> high stage: -> needs patch ___ Python tracker ___ ___ Python-bugs-list mail

[issue7466] Segmentation fault after about 20 seconds on lenovo T500

flox added the comment: Yes, confirmed too. Both 3.1 and 3.2 are broken. Minimal sequence to trigger the bug: """ ~ $ ./python Python 3.2a0 (py3k:76743M, Dec 10 2009, 12:19:41) [GCC 4.3.2] on linux2 Type "help", "copyright", "credits" or "license" for more information. """ def m(i): if

[issue7466] Segmentation fault after about 20 seconds on lenovo T500

Stefan Krah added the comment: Segfault confirmed on 64 bit Ubuntu, Python 3.2a0: Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7f5074dea6e0 (LWP 11665)] 0x0042111b in _PyTuple_Resize (pv=0x7fff7ce03b10, newsize=25) at Objects/tupleobject.c:853 853

[issue7466] Segmentation fault after about 20 seconds on lenovo T500

David W. Lambert added the comment: Further isolation, following change removes segmentation fault: digital_roots = tuple(map(digital_root,factorization)) becomes digital_roots = [digital_root(factor) for factor in factorization] --

[issue7466] Segmentation fault after about 20 seconds on lenovo T500

New submission from David W. Lambert : ''' This brute [possibly a] solution to http://projecteuler.net/index.php?section=problems&id=159 causes segmentation fault. $ p3 # an AMD 64 bit build. Python 3.1.1 (r311:74480, Oct 2 2009, 12:29:57) [GCC 4.3.3] on linux2 T