Built binaries on Linux machines segfault when gtsrcmaps or gtlike are called if not run on the machine they are built on. Stacktrace indicates that this is cause by a fault thrown during XML handling, specifically within the mutex lock handling of xerces-c. Operating theory is that this is similar to the gtltcubesun segfault issue, in that it may be that a destructor associated with the xml objects isn't being called/executed properly leading to an access issue and the subsequent failure by segmentation fault.
This only occurs on linux machines and does not occur when using the conda-forge provided binaries for linux architectures or if the tools are being run on a machine they were locally compiled on.
Issue can be replicated with build 2.4.90 when running either gtsrcmaps or gtlike on S3DF or any similar linux system.
Built binaries on Linux machines segfault when gtsrcmaps or gtlike are called if not run on the machine they are built on. Stacktrace indicates that this is cause by a fault thrown during XML handling, specifically within the mutex lock handling of xerces-c. Operating theory is that this is similar to the gtltcubesun segfault issue, in that it may be that a destructor associated with the xml objects isn't being called/executed properly leading to an access issue and the subsequent failure by segmentation fault.
This only occurs on linux machines and does not occur when using the conda-forge provided binaries for linux architectures or if the tools are being run on a machine they were locally compiled on.
Issue can be replicated with build 2.4.90 when running either gtsrcmaps or gtlike on S3DF or any similar linux system.