Custom handler for syscall.SIGBUS panicking on darwin/amd64

This page summarizes the projects mentioned and recommended in the original post on

Our great sponsors
  • Scout APM - Less time debugging, more time building
  • OPS - Build and Run Open Source Unikernels
  • SonarLint - Deliver Cleaner and Safer Code - Right in Your IDE of Choice!
  • GitHub repo The Go Play Space

    Advanced Go Playground frontend written in Go, with syntax highlighting, turtle graphics mode, and more

    This is a question out of curiosity, because I can't get what's causing this. Let's say we have this simple piece of code that doesn't do anything except waiting for SIGBUS/SIGTERM/SIGINT signals and exists on receiving one of them:

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts