Apple M2

[JetSetIlly]

Would anyone with access to a Mac with an M2 processor be able to help me debug an issue I'm having with Gopher2600?

The emulator has worked well for several years on Linux, Windows and MacOS
(Intel CPUs) but will immediately crash when compiled for MacOS with an M2.

The problem I'm having is that I don't have M2 hardware immediately available:

The error printed to stdout in the event of the crash is:

"signal 16 received but handler not on signal stack
fatal error: non-Go code set up signal handler without SA_ONSTACK flag"

Looking at the go.mod file we can see there are a couple of packages that might
be the cause of this and the documentation for the signal package explains why.

https://pkg.go.dev/os/signal#hdr-Go_programs_that_use_cgo_or_SWIG

Yes, this should be fixed but more importantly, there is some other error,
probably in my Go code, that is causing the signal to be raised.

The help I need therefore is:

1. Figuring out which package is not setting up a signal handler correctly
2. Finding the reason why the signal is being raised.

[JetSetIlly]

The remote testing I've managed to do so far, has established that the error is
in the GUI part of the program. If I run the emulator in terminal mode, there
is no crash.

My current educated guess is that it's a problem with how I'm using the GPU texture units and/or how I'm setting up the shaders.