I’m encountering some strange behavior with gmt backtracker. I have a set of locations with ages I am trying to backtrack but I keep getting this ERROR: Caught signal number 11 (Segmentation fault: 11) at
0 libsystem_platform.dylib 0x000000018e150864 _platform_strlen + 4
1 ??? 0x0000000000000100 0x0 + 256
Stack backtrace:
0 libgmt.6.4.0.dylib 0x000000010344e6f4 sig_handler_unix + 264
1 libsystem_platform.dylib 0x000000018e1534a4 _sigtramp + 56
2 libsystem_c.dylib 0x000000018dfff6a0 __vfprintf + 4544
3 libsystem_c.dylib 0x000000018e02d764 _vsnprintf + 224
4 libgmt.6.4.0.dylib 0x00000001032e2690 GMT_Report + 780
5 supplements.so 0x0000000106abd7ec GMT_backtracker + 1536
6 libgmt.6.4.0.dylib 0x00000001032eb14c GMT_Call_Module + 1332
7 gmt 0x000000010296dd50 main + 948
8 dyld 0x0000000102b4108c start + 520
The strange part is if I pip the coordinates / ages in, backtracker works fine e.g.
echo -37.8153 -31.4005 84.2 | gmt backtracker -ESAM-AFR > RGR_hot_spotted.xy
works, but when I try using a file, e.g.
gmt backtracker $RGR_locations -ESAM-AFR > RGR_hot_spotted.xy
I get the error. I’ve tried multiple different $RGR_location files to see if that was the issue but to no avail. The really strange thing is that it also occurs when I try and add a -M0.5 to backtracker. Even when I pip in coordinates / age like:
echo -37.8153 -31.4005 84.2 | gmt backtracker -ESAM-AFR -M0.5 > RGR_hot_spotted.xy
I will get the same segmentation fault error. Any ideas? Eventually I want to take a dataset of points with ages and backtrack them but using the -M0.5 scaling factor. Many thanks
- Peter