Zengtudor/pybind11
1
0
Fork 0
mirror of https://github.com/pybind/pybind11.git synced 2024-11-21 12:45:11 +00:00
Code Issues Packages Projects Releases Wiki Activity

Use :ref:deadlock-reference-label

Browse Source
This commit is contained in:
Ralf W. Grosse-Kunstleve 2024-10-07 16:37:56 -07:00
parent 5d0e95ca28
commit e5734d275f
No known key found for this signature in database
2 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/advanced/deadlock.md
View File

@ -1,3 +1,5 @@
.. _deadlock-reference-label:
# Double locking, deadlocking, GIL
[TOC]

8
docs/advanced/misc.rst
View File

@ -63,10 +63,8 @@ back into Python.
When writing C++ code that is called from other C++ code, if that code accesses
Python state, it must explicitly acquire and release the GIL. A separate
document on deadlocks [#f8]_ elaborates on a particularly subtle interaction
with C++'s block-scope static variable initializer guard mutexes.
.. [#f8] deadlock.md
document on :ref:`deadlock-reference-label` elaborates on a particularly subtle
interaction with C++'s block-scope static variable initializer guard mutexes.
The classes :class:`gil_scoped_release` and :class:`gil_scoped_acquire` can be
used to acquire and release the global interpreter lock in the body of a C++
@ -147,7 +145,7 @@ following checklist.
of exceptions.
- C++ static block-scope variable initialization that calls back into Python can
cause deadlocks; see [#f8]_ for a detailed discussion.
cause deadlocks; see :ref:`deadlock-reference-label` for a detailed discussion.
- You should try running your code in a debug build. That will enable additional assertions
within pybind11 that will throw exceptions on certain GIL handling errors