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.

Reply via email to