-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Segmentation fault during ctest in local build #512
Comments
Unlikely to be a memory leak issue. A SEG fault nearly always indicates a stray index or pointer in some loop. I'll have a look at this. I'm going to be fixing a working on a different issue to address #511 and it may need to edit the C test suite at that time anyway |
thank you! |
Hmm - I'm unable to reproduce that error. I didn't, however, run it through ctest but ran a local version I had just compiled in debug mode. Did that to address #511 already so thought I could find this potential bug easily that way. It is conceivable that building it in debug mode worked around what caused this problem. I've seen that more than once in the past. There could also be system or compiler difference - one of the motivations for using a docker container. For the record here are relevant configurations for the system I tried this on:
I have no idea how to proceed to try to resolve this other than see if it crops up again. |
thanks for working on this. It probably is related to my dev environment then. I will skip it for now and circle back when it's actually blocking something. |
When compiling mspass locally based on this guide, I was able to finish
and also installing the python package
However, when I ran
ctest
(this command is included in the cmake workflow file), the following error happened,Is this expected? Would it be related to the memory leak issue we discussed? 🤔
The text was updated successfully, but these errors were encountered: