Closed williballenthin closed 2 months ago
thank you for the feedback - i was being lazy. i'll add some test files and some test cases.
I would recommend testing on old go versions prior to 1.18 when buildinfo was added. I would also recommend testing with binaries emitted by garble
and gobfuscate
which can mess with symbol names. Otherwise LGTM with the above notes in mind
Tests are TODO / in progress? Getting the following when trying to resolve conflicts:
Failed to merge submodule tests/data (commits don't follow merge-base)
CONFLICT (submodule): Merge conflict in tests/data
Recursive merging with submodules currently only supports trivial cases.
Please manually handle the merging of each conflicted submodule.
This can be accomplished with the following steps:
- go to submodule (tests/data), and either merge commit 9f7f3c5
or update to an existing commit which has merged those changes
- come back to superproject and run:
git add tests/data
to record the above merge or update
- resolve any other conflicts in the superproject
- commit the resulting index in the superproject
Before continuing, I wanted to confirm what the status here was/is.
Yeah, I owe tests here. I believe the implementation is solid but without tests I can't prove it.
At a comfortable effort level, I could have this done in maybe two weeks. If there's a pending deadline, let me know and I can squeeze it in sooner.
This is not urgent at all! I just thought I may be able to lend a hand.
This is ready to go, but I had pulled in #2146 (instead of master), so we should merge that PR before this one.
use the strategies pioneered by GoReSym to detect the target OS for ELF binaries compiled by Go:
closes #1978 FYI @C0d3R3ad3r FYI @stevemk14ebr
Checklist