The code in Russ Cox's article does not race with the modern Go compiler.
But it's simple to fix that. Given arbitrary memory access within a Go process under Linux, can you see how to terminate the process and return 0 to the system?
Like calling os.Exit(0) when package os is unavailable.
https://research.swtch.com/gorace
The code in Russ Cox's article does not race with the modern Go compiler.
But it's simple to fix that. Given arbitrary memory access within a Go process under Linux, can you see how to terminate the process and return 0 to the system?
Like calling os.Exit(0) when package os is unavailable.