You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Starting program: ./venv/bin/python test.py
This GDB supports auto-downloading debuginfo from the following URLs:
<https://debuginfod.ubuntu.com>
Enable debuginfod for this session? (y or [n]) y
Debuginfod has been enabled.
To make this setting permanent, add 'set debuginfod enabled on' to .gdbinit.
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Downloading separate debug info for ./venv/lib/python3.11/site-packages/fitz/_extra.cpython-311-x86_64-linux-gnu.so
Downloading separate debug info for ./venv/lib/python3.11/site-packages/fitz/libmupdf.so.24.1
Downloading separate debug info for ./venv/lib/python3.11/site-packages/fitz/libmupdfcpp.so.24.1
Downloading separate debug info for ./venv/lib/python3.11/site-packages/fitz/_mupdf.so
Program received signal SIGSEGV, Segmentation fault.
0x00007ffff56e5ad2 in ?? () from ./venv/lib/python3.11/site-packages/fitz/libmupdf.so.24.1
The bug appears to be in the fitz package but I'm unsure where to file it.
Cheers
The text was updated successfully, but these errors were encountered:
Thanks for this very helpful package!
I just noticed a very strange bug occuring due to pymupdf.
The following sample code causes a segmentation fault:
Result with gdb:
The bug appears to be in the fitz package but I'm unsure where to file it.
Cheers
The text was updated successfully, but these errors were encountered: