Re: Tracking down a segmentation fault
Thanks to both Sean and Even for their responses.
I ended up compiling GDAL 3.3.0 (to include the debug symbols), then building rasterio on top of that. The backtrace (full bt is attached) now provides some more information:
#0 GDALDatasetPool::_CloseDatasetIfZeroRefCount (this=0x7fffb03c4940, pszFileName=pszFileName@entry=0x7fffa85946f0 "/vsis3/bucket/path/01.cog.tiff", pszOwner=pszOwner@entry=0x7fffa83c6eb0 "0x7fffa84f38c0") at gdalproxypool.cpp:378
Should I be moving this out of the rasterio list to GDAL? It might not be easy to replicate with GDAL alone though.
Thanks again for any thoughts,