avoid build ID mismatches when using -debugdir
A recent change added the -debugdir value to addGarbleToHash, which is part of the hash seed for all obfuscation taking place. In principle, it was okay to add, just like any other garble flag. In practice, it broke the added test case: > garble -debugdir ./debug1 build [stderr] # test/main FBi9xa6e.(*ac0bCOhR).String: relocation target FBi9xa6e.rV55e6H9 not defined qmECK6zf.init.0: relocation target qmECK6zf.eUU08z98 not defined [...] This is because -debugdir gets turned into an absolute path, and not all garble processes ended up using it consistently. The fix is rather simple; since -debugdir doesn't affect obfuscation, don't include it in the build hash seeding at all. Fixes #451.pull/453/head
parent
34cbd1b841
commit
ff803004d0
Loading…
Reference in New Issue