Eric K Richardson

Sometimes the definition of a `struct` is different from platform to platform and this was probably built using the macOS definition. Can you post the `struct` definition from `signal.h` header?

Well there is this as well - https://github.com/scala-native/scala-native/blob/main/posixlib/src/main/scala/scala/scalanative/posix/signal.scala#L47-L50 Strange that on C it is so large.

Not on my computer right now but the macOS porting guide mentions some float / int casting differences from x86 to arm. Maybe worth looking at?

Just to confirm, does the problem happen if you use release-fast for the test so it avoids debug symbols (no -g)?

It is the mode setting as seen here: https://scala-native.org/en/stable/user/sbt.html#sbt-settings-and-tasks Those settings are good as a default for release. (thin, releaseFast, and commix) Just an idea to see what happens.

The above could be something in the code or even the Scala Native code or optimization or maybe even clang. I was hoping it might just run but I think...

Due to various changes for features like naming the executable, cross compiling, running multiple mains, much of the configuration was moved into the build system and out of the external...

I think @tanishiking is probably correct. You have 2 choices, either make sure XCode is installed and updated correctly. It looks like now you do that via "Software update". ```sh...

Note: I think we also zero memory with `stackalloc`. This is not done in C so I am not sure why we do it but now in C it is...

I just think we should document both properly with the reasoning so it doesn't have to be tribal knowledge or dredged up through some forensic archeology. :-)