Open SecDbg opened 21 hours ago
Can you try if -debugdir="out"
helps?
Tried, used both debugdir="out"
and debugdir='out'
. Both gave the same result as above
PS C:\Users\Admin\Desktop\Test Garble> garble -debugdir='out' build .\main.go
unknown command: "Garble\\out"
unknown command: "Garble\\out"
go: error obtaining buildID for go tool compile: exit status 1
unknown command: "Garble\\out"
unknown command: "Garble\\out"
go: error obtaining buildID for go tool compile: exit status 1
go: error obtaining buildID for go tool compile: exit status 1
go: error obtaining buildID for go tool compile: exit status 1
exit status 1
PS C:\Users\Admin\Desktop\Test Garble>
Which shell is this? Can you try a different shell?
Do other options work OK for you?
I was using PowerShell originally, but tried doing it on cmd aswell. The result is the same I can use other flags like -tiny and -debug fine, but -debugdir just fails
This is on Windows 11, not sure if relevant. I don't currently have a VM running any other Windows version, so can't check if it works differently
What version of Garble and Go are you using?
What environment are you running Garble on?
go env
OutputWhat did you do?
I was looking to test Garble and wanted to look at the obfuscated output using -debugdir=out, as outlined in
garble -h
When I tried running the following, I got this outputWhat did you expect to see?
I expected to see an output directory, "out", with the obfuscated source so I could inspect it
What did you see instead?
I got the following errors:
Additional information
When I run garble -h to see the possible flags, I get this output
It states that -debugdir=out is a valid way of using -debugdir, but this does not work and gives the above error. Am I misunderstanding something, or is this an actual issue?