On Fri, Nov 20, 2020 at 12:48 PM 'Kevin Chowski' via golang-nuts <golang-nuts@googlegroups.com> wrote: > > I am debugging an issue in which we are seeing a crash on an atomic access; > on go 1.14.7 and 1.15.2 this reproduces with the following error: > > > panic: runtime error: invalid memory address or nil pointer dereference > > [signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x8049f7c] > > On gotip (go version devel +3fd4917 Fri Nov 20 20:02:47 2020 +0000 > linux/amd64) I see the following instead: > > > panic: unaligned 64-bit atomic operation > > (I'm glad the error message got better! Kudos to whomever did that.) > > My confusion is that I don't quite see this restriction being documented in > sync/atomic's docs: ctrl-f for "alignment" only reveals information related > to MIPS and ARM, whereas this issue is for Intel 386. Is this working as > intended (e.g. documentation bug) or is this something deeper?
It's down at the very bottom of https://golang.org/pkg/sync/atomic, in the "Bugs" section, which for some reason refers to i386 using the name x86-32. Ian -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/CAOyqgcX3F8zR2Y9ZYkkrkbZGWNj32o1j4RaYMtrc%3D%3DtW29kFLw%40mail.gmail.com.
