Date: Wed, 25 Nov 2015 01:01:25 +0000 From: bugzilla-noreply@freebsd.org To: python@FreeBSD.org Subject: [Bug 204793] www/mod_python35: Fatal Python error: PyEval_SaveThread: NULL tstate Message-ID: <bug-204793-21822-kXBEUuHg0O@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-204793-21822@https.bugs.freebsd.org/bugzilla/> References: <bug-204793-21822@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204793 Kubilay Kocak <koobs@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |python@FreeBSD.org Keywords| |crash, needs-qa URL| |https://github.com/grisha/m | |od_python/issues/46 --- Comment #1 from Kubilay Kocak <koobs@FreeBSD.org> --- Backtraces from the coredumps (as attachments) might prove useful. If mod_python (and/or Apache) can be built with DEBUG options and the symptom is still reproducible, it might be worth enabling that too. I also see this issue upstream (CentOS) https://github.com/grisha/mod_python/issues/46 Please add your information there as well -- You are receiving this mail because: You are on the CC list for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-204793-21822-kXBEUuHg0O>