debugging extensions when installing with "pip install -e ."

[nurpax]

I'm developing an extension and the primary way I'm currently testing is by doing basically this:

pip install -e .
python test/test.py

Alas, I'm hitting a segfault in my extension, so I'm trying to run it under gdb or lldb. I couldn't get this to print any kind of stack trace on Windows (maybe due to this?), but I can debug on Linux so no problem there.

However, when installing with pip install -e ., it seems like the extension is built for release. I don't know cmake well enough to know how to make pip install build a debug build instead.

Anyone happen to know?

(And yeah, my workflow currently is really cumbersome as it takes a long time to iterate through pip install -e. I just couldn't figure out yet what's a better way to get everything working without a pip install into a venv.)

[nurpax]

Found a solution. Adding the below to pyproject.toml switches to debug build.

[tool.scikit-build]
cmake.build-type = "Debug"