Ok, will do. Ian Lance Taylor <i...@golang.org> ezt írta (időpont: 2016. jún. 26., V, 22:53):
> On Sun, Jun 26, 2016 at 1:28 PM, Tamás Gulácsi <tgulacs...@gmail.com> > wrote: > > > > 2016. június 26., vasárnap 21:42:15 UTC+2 időpontban Ian Lance Taylor a > > következőt írta: > >> > >> On Sun, Jun 26, 2016 at 12:18 AM, Tamás Gulácsi <tgula...@gmail.com> > >> wrote: > >> > I want to find out the source package's given the binary. > >> > > >> > github.com/FiloSottile/gorebuild (and github.com/rjeczalik/which) > works > >> > fine > >> > with binaries built with the "go" tool. > >> > But fails if cgo (and thus I think gcc) is included in the build > >> > procedure. > >> > > >> > A minimal example is attached to > >> > https://github.com/FiloSottile/gorebuild/issues/3 > >> > > >> > Can anybody help me? > >> > >> I don't see how the .gosymtab section is relevant here. It's > >> currently always empty. When using external linking, as when building > >> a program that uses cgo, it gets dropped. But even when it remains in > >> the file, it is empty. I don't think gosymtab has had any contents > >> since the 1.2 release. Yes, the situation is somewhat confusing, and > >> I'm not sure I entirely understand it. > >> > >> Ian > > > > > > Ok, than anz other idea to get the binary's main.main function's > package's > > path, from the binary? > > The other way around (go list -e .../binary) has its own weaknesses (dirs > > with same names)... > > If you're happy with gorebuild, keep using it. Just change it so that > it doesn't care if there is no .gosymtab section, and to treat a > missing .gosymtab section as an empty one. > > Ian > -- 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.
