Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
x/tools/go/pointer: crash in solver #25090
TODO: look through the 1.7GB log file and identify what's up with node n31786.
Not sure if this is the same issue, but comparing just stack traces it seems that the panic occurs somewhere else in the code. I'll put this here since it seems related either way.
Origin of the issue: TrueFurby/go-callvis#24
referenced this issue
Jan 19, 2019
I don't know much about how the analysis internally works in pointer package, but I tried to add some extra debugs here and there, until I saw something relevant..
This has something to do with this call in close(), which might be tricky for the pointer analysis I suspect.. or perhaps it catches some rare case when the graph data is not calculated properly?
and here's more of the log output just before panic (not sure if it's gonna be helpful):