logger() function returns segmentation fault on MacOS

[ananyak12]

Hello, I have been trying to run the example in the "Setting and Recording Module Variables" subsection of the Fundamentals of Basilisk Simulation, and keep running into a segmentation fault each time I execute it. The path for the file in question is - basilisk/docs/source/codeSamples/bsk-6.py

https://hanspeterschaub.info/basilisk/Support/bskKnownIssues.html - Upon going through this resource I see that it has been reported as a known issue in the most recent version of Basilisk(which I am running).

I have also attached a screenshot of the error message I receive when I execute this program

As for my system specs, I am running this on a MacBook Pro, Apple M3 Pro Chip (18GB RAM), MacOS Sonoma 14.5.

[juan-g-bonilla]

Hello @ananyak12 , thanks for opening this discussion.

I am not really sure that this bug and the one that is mentioned in the known issues page are the same. The bug in "known issues" states that the bug appears with more than one task, while the code sample you tried running only has one task. Happy to help you debug this one, but I think it's important to figure out whether these two bugs are actually related.

Regarding this bug: I do not have a mac and this runs without issue in my computer, so I'm going to have trouble gathering information. Have you ever used a debugger with Basilisk? That would be immensely valuable here since it would give us the spot where the segfault is being raised. Other than that, I would try to clean-build Basilisk and ensure all your compilation options are setup correctly for your system. Segfaults are insidious and could be caused by incorrect compiling.

[ananyak12]

Thanks for the insight! I was able to get the logger functionality to work on my system by downgrading the Python version from 3.12 to 3.9.6. I'm not too sure how that helped but I'm relieved that it finally works now

[schaubh]

I can run bsk-6.py tutorial script on my macBook without issues?

[ananyak12]

Thank you for checking Professor @schaubh! I guess it was an issue with the Python version. There seems to be some compatibility issue with 3.12. Downgrading it to 3.9.6 helped resolve this issue for me