Closed mappu closed 5 years ago
Thanks for your report! I made a change to include 'initdone·', please try it out.
Thanks! Just confirming that did make a big improvement.
Although it didn't seem to affect the tree visualisation in a any material way for my binary.
There are some remaining errors, but very little that points to Go/C code in a specific way.
Could you attach the full output of go tool nm -size
on your binary. I'd like to understand these formats more.
Hi! Super cool tool.
I am running this with Go 1.10
windows/amd64
from golang.org, and Python 3.6 from Cygwin64, on a mixed Go/C (CGO) binary, built withgo build
and nothing more (no-s -w
etc).Many such errors during
tab2pydic.py
pass: some representative onesSeems to mostly work aside from this, but the resulting visualisation has a large UNKNOWN section, i guess that's related?