pikepdf does a complex job in providing bindings from Python to a C++ library,
both of which have different ideas about how to manage memory. This page
documents some methods that may help should it be necessary to debug the Python
C++ extension (
Compiling a debug build of QPDF
It may be helpful to create a debug build of QPDF.
Download QPDF and compile a debug build:
# in QPDF source tree
./configure CFLAGS='-g -O0' CPPFLAGS='-g -O0' CXXFLAGS='-g -O0'
Compile and link against QPDF source tree
pikepdf._qpdf against the version of QPDF above, rather than the
env QPDF_SOURCE_TREE=<location of QPDF> python setup.py build_ext --inplace
When running Python, ensure that you override shared library load locations:
env LD_LIBRARY_PATH=$QPDF_SOURCE_TREE/libqpdf/build/.libs python ...
# macOS - may require disabling System Integrity Protection
env DYLD_LIBRARY_PATH=$QPDF_SOURCE_TREE/libqpdf/build/.libs python ...
You can also run Python through a debugger (
lldb) in this manner,
and you will have access to the source code for both pikepdf’s C++ and QPDF.
Valgrind may also be helpful - see the Python documentation for information
on setting up Python and Valgrind.