http://bugzilla.opensuse.org/show_bug.cgi?id=1156336 http://bugzilla.opensuse.org/show_bug.cgi?id=1156336#c18 --- Comment #18 from Aleksa Sarai <asarai@suse.com> --- I've been staring at the coredumps for a few hours, and it's not making sense. It looks like Go is just aborting the process in both of them: % dlv core /usr/bin/lxd lxd.core (dlv) grs Goroutine 1 - User: /usr/lib64/go/1.11/src/runtime/netpoll.go:173 internal/poll.runtime_pollWait (0x55bb0c670c78) Goroutine 2 - User: /usr/lib64/go/1.11/src/runtime/proc.go:303 runtime.gopark (0x55bb0c676371) * Goroutine 17 - User: /usr/lib64/go/1.11/src/runtime/sys_linux_amd64.s:146 runtime.raise (0x55bb0c6a64b4) (thread 29109) Goroutine 18 - User: /usr/lib64/go/1.11/src/runtime/proc.go:303 runtime.gopark (0x55bb0c676371) Goroutine 19 - User: /usr/lib64/go/1.11/src/runtime/proc.go:303 runtime.gopark (0x55bb0c676371) Goroutine 22 - User: /usr/lib64/go/1.11/src/runtime/sigqueue.go:139 os/signal.signal_recv (0x55bb0c68b2ce) (thread 29096) Goroutine 26 - User: /usr/lib64/go/1.11/src/database/sql/sql.go:1001 database/sql.(*DB).connectionOpener (0x55bb0ca6bf4a) Goroutine 27 - User: /usr/lib64/go/1.11/src/database/sql/sql.go:1014 database/sql.(*DB).connectionResetter (0x55bb0ca6c07d) Goroutine 31 - User: /usr/lib64/go/1.11/src/runtime/proc.go:303 runtime.gopark (0x55bb0c676371) Goroutine 32 - User: /usr/lib64/go/1.11/src/runtime/proc.go:303 runtime.gopark (0x55bb0c676371) Goroutine 34 - User: /usr/lib64/go/1.11/src/runtime/proc.go:303 runtime.gopark (0x55bb0c676371) Goroutine 35 - User: /usr/lib64/go/1.11/src/runtime/proc.go:303 runtime.gopark (0x55bb0c676371) Goroutine 58 - User: /usr/lib64/go/1.11/src/runtime/netpoll.go:173 internal/poll.runtime_pollWait (0x55bb0c670c78) Goroutine 59 - User: /usr/lib64/go/1.11/src/runtime/netpoll.go:173 internal/poll.runtime_pollWait (0x55bb0c670c78) Goroutine 62 - User: /usr/lib64/go/1.11/src/database/sql/sql.go:1001 database/sql.(*DB).connectionOpener (0x55bb0ca6bf4a) Goroutine 63 - User: /usr/lib64/go/1.11/src/database/sql/sql.go:1014 database/sql.(*DB).connectionResetter (0x55bb0ca6c07d) Goroutine 64 - User: /usr/lib64/go/1.11/src/runtime/sys_linux_amd64.s:532 runtime.futex (0x55bb0c6a6a03) (thread 29108) Goroutine 66 - User: /usr/lib64/go/1.11/src/runtime/sys_linux_amd64.s:532 runtime.futex (0x55bb0c6a6a03) (thread 29093) (dlv) bt 0 0x000055bb0c6a64b4 in runtime.raise at /usr/lib64/go/1.11/src/runtime/sys_linux_amd64.s:146 1 0x000055bb0c6a4b81 in runtime.goexit at /usr/lib64/go/1.11/src/runtime/asm_amd64.s:1333 The main takeaway is that the segfault isn't happening in the C library (though I'm not sure if delve understands how to load symbols from shared libraries when debugging coredumps). But it's incredibly strange to get a segfault from within Go code without an associated panic() stacktrace. I'm going to install Leap on an older laptop and see if I can reproduce the issue there... -- You are receiving this mail because: You are on the CC list for the bug.