Ah, I gotcha. OK, off I go to dig for unsafe.Pointer and cgo usages in a dependency :)
Thanks! Jim On Wednesday, December 7, 2016 at 1:04:23 AM UTC-5, Dave Cheney wrote: > > > > On Wednesday, 7 December 2016 12:52:17 UTC+9, brik...@gmail.com wrote: >> >> 0xb01dfacedebac1e is a poison pill that usually indicates misuse of >>> unsafe.Pointer. If there is any use of unsafe.Pointer or CGO in the program >>> that would be a good place to start looking. >>> >> >> Interesting. As far as I know, we don't use unsafe.Pointer or cgo >> anywhere in the code, but I'll poke around. Maybe some dependency of ours >> does. >> >> Also, The particular line of code that leads to one of the panics is deep >> inside Go logger Printf code, so I'm not sure how anything in my code could >> lead to that? >> > > The memory corruption probably happened before that line. If there is a > data race in the program, then all bets are off. > > >> >> Thanks, >> Jim >> >> On Tuesday, December 6, 2016 at 10:29:45 PM UTC, r...@golang.org wrote: >>> >>> >>> 0xb01dfacedebac1e is a poison pill that usually indicates misuse of >>> unsafe.Pointer. >>> If there is any use of unsafe.Pointer or CGO in the program that would >>> be a good >>> place to start looking. >>> >>> You can google "0xb01dfacedebac1e" for more details. >>> >>> >>> >>> On Tuesday, December 6, 2016 at 5:00:37 PM UTC-5, brik...@gmail.com >>> wrote: >>>> >>>> Hi folks, >>>> >>>> We're using Go to write an open source CLI tool called terragrunt >>>> <https://github.com/gruntwork-io/terragrunt>. We cross-compile >>>> binaries for the tool for multiple OS's. Some of the users are reporting >>>> intermittent crashes due to mysterious panic errors. Here are two examples: >>>> >>>> - https://github.com/gruntwork-io/terragrunt/issues/41 (crash log >>>> <https://gist.github.com/antonbabenko/9eae6e5ded37633307d78894e1b6c833> >>>> ) >>>> - https://github.com/gruntwork-io/terragrunt/issues/68 (crash log >>>> <https://gist.github.com/jdubeau123/6f5286fd43019bf66b71ca62e5a0cafe> >>>> ) >>>> >>>> The panics seem to happen in strange places. For example, one happens >>>> deep in a call to the Printf method of a logger. Another in malloc. >>>> >>>> We're at a loss for how to debug these as this doesn't seem to be >>>> caused by the usual culprits (e.g. a nil in the code) and can only be >>>> reproduced intermittently. Any suggestions? >>>> >>>> Thanks, >>>> Jim >>>> >>> -- 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.
