And which bulitin package will call cgo or runtime.LockOSThread. In my project, I used packages net, io, sync.
在 2016年8月16日星期二 UTC+8上午1:15:29，Ian Lance Taylor写道： > > On Mon, Aug 15, 2016 at 1:21 AM, <lime...@gmail.com <javascript:>> > wrote: > > > > In goroutine stack dump there is a dead lock. > > > > goroutine 17 [syscall, 214 minutes, locked to thread]: > > runtime.goexit() > > /root/go/src/runtime/asm_amd64.s:1998 +0x1 > > > > > > No more information, just this. I don't know how to debug it. Somebody > can > > help me? > > That is not a deadlock, at least not a deadlock in the Go program. It > is normal for a goroutine to be locked to a thread. It can happen > because of cgo, or because the code called runtime.LockOSThread. It > is not a problem. The problem is that the thread has not made any > progress for 214 minutes; what that is depends on what it is doing. > > If this is repeatable, can you get a stack trace with the environment > variable GOTRACEBACK=system ? > > 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. For more options, visit https://groups.google.com/d/optout.
