Open edwardhartnett opened 1 year ago
I believe this is related to an issue I'd been seeing with ip unit tests segfaulting on my personal computer. Based on what I found here, I tried increasing the stack limit (ulimit -s unlimited
) and that fixed it. I'm guessing this is why Kyle put the ulimit -s unlimited
line in ip's Intel CI. The same thing happens if I try to use the other interpolation schemes, i.e., they segfault unless I unset the stack limit. I'm still working on figuring out how much of it is a code issue per se vs. compiler issues.
This is happening for intel compilers only.
However, the grb_util utilities are riddled with memory bugs, except degrib2, which I've cleaned up. The others have never been able to pass any kind of memory checking.
However, no package should segfault if it can check parameters and return an error instead, so this error should be reduced to a unit test in ip, and then we can decide how ip should handle it instead of segfaulting.
Meanwhile, I will take a look at the memory problems in copygb2 and see if I can fix some of them...