Closed glycerine closed 9 years ago
So odd. This reproduced a couple of times, then just now it started working(!) Closing because I can't repro any longer.
Strange. Here's a guess: godebug.EnteringNewScope was recently renamed to godebug.EnteringNewFile. If you updated the code in your directory by running "git pull" but didn't run "go install github.com/mailgun/godebug", then you would have been using an older code-generating binary that outputted godebug.EnteringNewScope calls, and they would fail to link against the new library that only had godebug.EnteringNewFile calls.
Could that be the case?
Ah. Good to know. Was probably using an out of date binary.
e57fb7e2aae9c6aa79ad007957f2ca32fc7b74fa
Hi @jeremyschlatter, having some trouble trying the latest godebug. go1.4.2. centos6.6/amd64. Please advise. Thanks!
Jason
again with -godebugwork and the start of the output shown