On Mon, Sep 19, 2016 at 6:34 PM, Wanghb Wang <wangh...@gmail.com> wrote: > > > 在 2016年9月20日星期二 UTC+8上午3:41:09，Ian Lance Taylor写道： >> >> On Mon, Sep 19, 2016 at 8:34 AM, Wanghb Wang <wang...@gmail.com> wrote: >> > >> > when I use stattcpupprof in my program, I got fatal error malloc >> > deadlock. >> > delete the cpu pprof, the program run well. >> > >> > >> > my question is : >> > Does startcpuprof infect the malloc or resulting OOM Problem >> >> I'm sorry, I don't understand the question. >> >> >> > this is my panic stack trace: >> >> It looks like you have C code that calls goCbStr. Somehow when that >> happens the malloc lock is held for the thread. The only way I can >> see that happening is if your C code has a SIGPROF handler that calls >> into Go. >> > > However, I have no SIGPROF handler(you mean sigaction(SIGPROF,&act,NULL)?)
Yes, that kind of thing. > my question is: > why I add startcpupprof in my golang program (I did have C calls into Go) > result in malloc deadlock? I don't know. Sorry. If you can tell us precisely how to recreate the problem ourselves--what program to run--please open an issue at https://golang.org/issue. Thanks. 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.
