mirror of
https://github.com/pybind/pybind11.git
synced 2024-11-24 22:25:10 +00:00
Updated Debugging segfaults and hard to decipher pybind11 bugs (markdown)
parent
8eae6eb2a4
commit
20cf48052d
@ -47,7 +47,7 @@ def traced(func, ignoredirs=None):
|
|||||||
|
|
||||||
Usage of this could look like the following:
|
Usage of this could look like the following:
|
||||||
|
|
||||||
```sh
|
```py
|
||||||
import debug
|
import debug
|
||||||
import my_crazy_cool_module # Say this has bindings buried 3 levels deep.
|
import my_crazy_cool_module # Say this has bindings buried 3 levels deep.
|
||||||
|
|
||||||
@ -69,13 +69,13 @@ The easiest way to do this is to use a debug build w/ a debug Python interpreter
|
|||||||
|
|
||||||
Here's an example workflow of debugging a specific unittest on CPython 3.8 on Ubuntu 18.04; this assumes the following packages are installed:
|
Here's an example workflow of debugging a specific unittest on CPython 3.8 on Ubuntu 18.04; this assumes the following packages are installed:
|
||||||
|
|
||||||
```
|
```sh
|
||||||
sudo apt install cmake build-essential python3.8-dev python3.8-venv python3.8-dbg
|
sudo apt install cmake build-essential python3.8-dev python3.8-venv python3.8-dbg
|
||||||
```
|
```
|
||||||
|
|
||||||
Then here's an example of running a unittest with GDB:
|
Then here's an example of running a unittest with GDB:
|
||||||
|
|
||||||
```
|
```sh
|
||||||
cd pybind11
|
cd pybind11
|
||||||
|
|
||||||
python3.8-dbg -m venv ./venv
|
python3.8-dbg -m venv ./venv
|
||||||
|
Loading…
Reference in New Issue
Block a user