go: runtime: "unexpected return pc for runtime.sigpanic" in x/sys/unix on darwin-amd64-10_12

2021-04-21T22:16:51-33663a6/darwin-amd64-10_12 2021-04-20T20:58:09-ac73e9f/darwin-amd64-10_12 2021-04-20T07:25:15-93ed5bc/darwin-amd64-10_12 2021-04-19T17:01:43-37df388/darwin-amd64-10_12 2021-04-15T04:56:47-66c3f26/darwin-amd64-10_12

fatal error: unexpected signal during runtime execution
[signal SIGSEGV: segmentation violation code=0x1 addr=0xb01dfacedebac1e pc=0x7fffe85a3561]

runtime stack:
runtime: unexpected return pc for runtime.sigpanic called from 0x7fffe85a3561
stack: frame={sp:0x7000063272f8, fp:0x700006327348} stack=[0x7000062a8278,0x700006327e78)
0x00007000063271f8:  0x0100700006327218  0x0000000000000004 
0x0000700006327208:  0x000000000000001f  0x00007fffe85a3561 
0x0000700006327218:  0x0b01dfacedebac1e  0x0000000000000001 
0x0000700006327228:  0x00007000063272c8  0x0000000001036131 <runtime.throw+0x0000000000000071> 
0x0000700006327238:  0x00000000011a730c  0x0000700006327280 
0x0000700006327248:  0x00000000010363e8 <runtime.fatalthrow.func1+0x0000000000000048>  0x000000c000000d80 
0x0000700006327258:  0x0000000000000001  0x0000000000000001 
0x0000700006327268:  0x00007000063272c8  0x0000000001036131 <runtime.throw+0x0000000000000071> 
0x0000700006327278:  0x000000c000000d80  0x00007000063272b8 
0x0000700006327288:  0x0000000001036370 <runtime.fatalthrow+0x0000000000000050>  0x0000700006327298 
0x0000700006327298:  0x00000000010363a0 <runtime.fatalthrow.func1+0x0000000000000000>  0x000000c000000d80 
0x00007000063272a8:  0x0000000001036131 <runtime.throw+0x0000000000000071>  0x00007000063272c8 
0x00007000063272b8:  0x00007000063272e8  0x0000000001036131 <runtime.throw+0x0000000000000071> 
0x00007000063272c8:  0x00007000063272d0  0x0000000001036160 <runtime.throw.func1+0x0000000000000000> 
0x00007000063272d8:  0x00000000011aa0b5  0x000000000000002a 
0x00007000063272e8:  0x0000700006327338  0x000000000104c056 <runtime.sigpanic+0x0000000000000396> 
0x00007000063272f8: <0x00000000011aa0b5  0x0000000000000000 
0x0000700006327308:  0x0000000000000000  0x000000000000000a 
0x0000700006327318:  0x0000000001344000  0x000000000000000a 
0x0000700006327328:  0x0000000001347a00  0x000000000134a200 
0x0000700006327338:  0x0000700006327418 !0x00007fffe85a3561 
0x0000700006327348: >0x0000000001347a00  0x000000000134aa78 
0x0000700006327358:  0x0000000000000000  0x0000000000000000 
0x0000700006327368:  0x000000000134aa50  0x0000000000000000 
0x0000700006327378:  0x000000000134aa58  0x000000000134aa68 
0x0000700006327388:  0x0000000000002800  0x0000000000000000 
0x0000700006327398:  0x000000000134aa70  0x0000000000000004 
0x00007000063273a8:  0x000000000134a200  0x00000000000000a0 
0x00007000063273b8:  0x000000000134a204  0x000000000000000a 
0x00007000063273c8:  0x00000000010678ad <runtime.asmcgocall+0x00000000000000ad>  0xfffffffffffffe00 
0x00007000063273d8:  0x0000000001344000  0xff80000000001004 
0x00007000063273e8:  0x000070000632ffff  0x0000000000000000 
0x00007000063273f8:  0x0000000000000000  0x0000000000000000 
0x0000700006327408:  0x00007ffff125f000  0x00000000000000a0 
0x0000700006327418:  0x0000700006327448  0x00007fffe85a32da 
0x0000700006327428:  0x00000000000000a0  0x0000000000000000 
0x0000700006327438:  0x0000000000000003  0xc798bd940d93005d 

This may have the same root cause as #45700, but the fact that it only occurs on the 10_12 builder (and occurs consistently there) is a bit strange.

CC @cherrymui

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Comments: 18 (16 by maintainers)

Commits related to this issue

Most upvoted comments

Thanks @mark-rushakoff !

I think we can call this issue fixed. macOS 10.12 is no longer supported. And other failures reported in the issue are fixed.