Thanks Ian! Removing UPX solved the problem. On Tue, Mar 15, 2022 at 9:25 PM Ian Lance Taylor <i...@golang.org> wrote: > > On Tue, Mar 15, 2022 at 9:09 PM Stavros Filargyropoulos > <stav...@pensando.io> wrote: > > > > On an embedded 16 core arm device we have been observing infrequent runtime > > crashes, with different signatures every time. > > > > One examples is this: > > > > unexpected fault address 0x6b6fc6da > > fatal error: fault > > [signal SIGSEGV: segmentation violation code=0x1 addr=0x6b6fc6da pc=0x7f72c] > > > > goroutine 1 [running, locked to thread]: > > runtime.throw(0xc3074, 0x5) > > /usr/local/go/src/runtime/panic.go:1116 +0x54 fp=0x4000072c20 > > sp=0x4000072bf0 pc=0x3dcc4 > > runtime.sigpanic() > > /usr/local/go/src/runtime/signal_unix.go:749 +0x3b8 fp=0x4000072c50 > > sp=0x4000072c20 pc=0x51b48 > > reflect.(*rtype).Method(0xc55fe, 0x14, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, > > 0x0, ...) > > /usr/local/go/src/reflect/type.go:809 +0xcc fp=0x4000072de0 > > sp=0x4000072c60 pc=0x7f72c > > runtime: unexpected return pc for runtime.doInit called from 0x4000098060 > > ... > > > This is with go version go1.15.11 linux/amd64, cross compiling for arm64. > > CGO disabled. > > There have been some fixes in this area. Is it possible for you to > try the new 1.18 release to see if the problem still happens? (Note > that we no longer support 1.15.) > > > We also use upx version 3.95 > > There have been some reported problems using upx with Go binaries. Is > it possible for you to try not using upx to see if the problem still > happens? > > 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/CAPZF_5a5Jspwqero-Wh%3DQy94JkQNRRGFF8%3Dfk8Qan%3Dnnw%2BLX0A%40mail.gmail.com.
