Hunting Down a Go Runtime Bug on 32-Bit Embedded Systems

Very interesting read, these bugs that only happen after a lot of time in production are the worse to troubleshoot

Go was born into 64-bit era, I remember seeing many more bugs that only occur on 32-bit systems. I'm pretty certain the observation in the article is correct that no one at Google tests Go on anything apart from 64-bit ARM/x86 Linux

So a stronger type system in the boundary between Go and Linux would have caught this?

Not directly related to your embedded Go bug, but maybe helpful:

What really sky-rocketed my debugging skills in embedded devices was learning to utilize the Python plugin interface of 'gdb'.

Isn't this something that software developers do everyday?

I wonder what other 32 bit bugs are waiting to be discovered.