e83990a872
This check is triggered by nested pyuno PyThreadAttach instances. The assertion is basically about having multiple PyThreadState instances per OS thread. Hopefully this is not a "real" problem and the other checks in PyEval_ReleaseThread/PyEval_AcquireThread will find all "real" problems. http://www.mail-archive.com/libreoffice@lists.freedesktop.org/msg62195.html Change-Id: Ia82135f37f55ea69b545a83098619939869cb7c5 Reviewed-on: https://gerrit.libreoffice.org/3453 Reviewed-by: David Ostrovsky <David.Ostrovsky@gmx.de> Tested-by: David Ostrovsky <David.Ostrovsky@gmx.de>
15 lines
689 B
Groff
15 lines
689 B
Groff
disable a check in PyThreadState_Swap that is hopefully not a "real" problem
|
|
|
|
--- python3/Python/pystate.c 2013-04-17 22:45:00.799800000 +0200
|
|
+++ python3/Python/pystate.c 2013-04-17 22:46:53.743800000 +0200
|
|
@@ -437,7 +437,9 @@
|
|
to be used for a thread. Check this the best we can in debug
|
|
builds.
|
|
*/
|
|
-#if defined(Py_DEBUG) && defined(WITH_THREAD)
|
|
+#if defined(Py_DEBUG) && defined(WITH_THREAD) && 0
|
|
+ /* disable this for LO - it is triggered by nested PyThreadAttach
|
|
+ which do not appear to be a real problem */
|
|
if (newts) {
|
|
/* This can be called from PyEval_RestoreThread(). Similar
|
|
to it, we need to ensure errno doesn't change.
|