I've come up with a quicky&dirty script
https://github.com/rouault/symbol_clash_detector/blob/master/symbol_clash_detector.py
that works only for Linux and attempts to find C symbol clashes in the
.so files loaded in a process (C++ is trickier because due to template &
inline code, functions fr
Paul,
Looking at
https://stackoverflow.com/questions/63161532/python-segmentation-fault-when-using-zipfile-while-gdal-package-loaded
shows an interesting thing in a gdb backtrace
|#0 0x77e3aa50 in free () from /usr/lib/libc.so.6 #1
0x7485ae0f in inflateReset2 () from /usr/lib
This may not be a GDAL bug and as such I have not raised it as an issue but
I wanted to put it here for anyone else who comes across the same problem.
There does appear to be some interference between, at least the conda
distribution of, GDAL and something else within Python causing a
segmentation
