Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Runtime panic when running docker-mirror built with Go 1.17 on macOS #96

Open
dwickr opened this issue Nov 29, 2021 · 1 comment
Open

Comments

@dwickr
Copy link

dwickr commented Nov 29, 2021

After building with go build using Go 1.17 on macOS, docker-mirror panics:

$ go version
go version go1.17.3 darwin/amd64
$ go build
$ ./docker-mirror --help
fatal error: unexpected signal during runtime execution
[signal SIGSEGV: segmentation violation code=0x1 addr=0xb01dfacedebac1e pc=0x7fff20412c9e]

runtime stack:
runtime: unexpected return pc for runtime.sigpanic called from 0x7fff20412c9e
stack: frame={sp:0x7ffeefbff368, fp:0x7ffeefbff3b8} stack=[0x7ffeefb80408,0x7ffeefbff470)
0x00007ffeefbff268:  0x01007ffeefbff288  0x0000000000000004
0x00007ffeefbff278:  0x000000000000001f  0x00007fff20412c9e
0x00007ffeefbff288:  0x0b01dfacedebac1e  0x0000000000000001
0x00007ffeefbff298:  0x0000000004035fd1 <runtime.throw+0x0000000000000071>  0x00007ffeefbff338
0x00007ffeefbff2a8:  0x0000000004423a1c  0x00007ffeefbff2f0
0x00007ffeefbff2b8:  0x0000000004036288 <runtime.fatalthrow.func1+0x0000000000000048>  0x0000000004719840
0x00007ffeefbff2c8:  0x0000000000000001  0x0000000000000001
0x00007ffeefbff2d8:  0x00007ffeefbff338  0x0000000004035fd1 <runtime.throw+0x0000000000000071>
0x00007ffeefbff2e8:  0x0000000004719840  0x00007ffeefbff328
0x00007ffeefbff2f8:  0x0000000004036210 <runtime.fatalthrow+0x0000000000000050>  0x00007ffeefbff308
0x00007ffeefbff308:  0x0000000004036240 <runtime.fatalthrow.func1+0x0000000000000000>  0x0000000004719840
0x00007ffeefbff318:  0x0000000004035fd1 <runtime.throw+0x0000000000000071>  0x00007ffeefbff338
0x00007ffeefbff328:  0x00007ffeefbff358  0x0000000004035fd1 <runtime.throw+0x0000000000000071>
0x00007ffeefbff338:  0x00007ffeefbff340  0x0000000004036000 <runtime.throw.func1+0x0000000000000000>
0x00007ffeefbff348:  0x000000000442aa54  0x000000000000002a
0x00007ffeefbff358:  0x00007ffeefbff3a8  0x000000000404b776 <runtime.sigpanic+0x0000000000000396>
0x00007ffeefbff368: <0x000000000442aa54  0x0000000004719840
0x00007ffeefbff378:  0x00007ffeefbff3e8  0x00000000040292a6 <runtime.(*mheap).allocSpan+0x0000000000000546>
0x00007ffeefbff388:  0x000000c00020c000  0x0000000000002000
0x00007ffeefbff398:  0x0000000000000008  0x0000000004719840
0x00007ffeefbff3a8:  0x00007ffeefbff3f0 !0x00007fff20412c9e
0x00007ffeefbff3b8: >0x00007ffeefbff3f0  0x00000000046bc000
0x00007ffeefbff3c8:  0x0000000000000648  0x000000000427fa05 <golang.org/x/sys/unix.libc_ioctl_trampoline+0x0000000000000005>

I can include more of the traceback if you want but it doesn't seem super useful.

Seems like updating the x/sys package will address this issue. From golang/go#46763

@josegonzalez
Copy link
Contributor

Pull requests welcome :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants