How to Use control Flow ?

[furax124]

What version of Garble and Go are you using?

$ garble version
 v0.12.1
$ go version
go1.21.3

What environment are you running Garble on?

go env Output

$ go env
set GO111MODULE=on
set GOARCH=amd64
set GOBIN=
set GOCACHE=C:\Users\vodan\AppData\Local\go-build
set GOENV=C:\Users\vodan\AppData\Roaming\go\env
set GOEXE=.exe
set GOEXPERIMENT=
set GOFLAGS=
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOINSECURE=
set GOMODCACHE=C:\Users\vodan\go\pkg\mod
set GONOPROXY=
set GONOSUMDB=
set GOOS=windows
set GOPATH=C:\Users\vodan\go
set GOPRIVATE=
set GOPROXY=https://proxy.golang.org,direct
set GOROOT=C:/Users/vodan/go/pkg/mod/golang.org/toolchain@v0.0.1-go1.21.3.windows-amd64
set GOSUMDB=sum.golang.org
set GOTMPDIR=
set GOTOOLCHAIN=auto
set GOTOOLDIR=C:\Users\vodan\go\pkg\mod\golang.org\toolchain@v0.0.1-go1.21.3.windows-amd64\pkg\tool\windows_amd64
set GOVCS=
set GOVERSION=go1.21.3
set GCCGO=gccgo
set GOAMD64=v1
set AR=ar
set CC=gcc
set CXX=g++
set CGO_ENABLED=0
set GOMOD=C:\Users\vodan\Desktop\Random_Things\go.mod
set GOWORK=
set CGO_CFLAGS=-O2 -g
set CGO_CPPFLAGS=
set CGO_CXXFLAGS=-O2 -g
set CGO_FFLAGS=-O2 -g
set CGO_LDFLAGS=-O2 -g
set PKG_CONFIG=pkg-config
set GOGCCFLAGS=-m64 -fno-caret-diagnostics -Qunused-arguments -Wl,--no-gc-sections -fmessage-length=0 -ffile-prefix-map=C:\Users\vodan\AppData\Local\Temp\go-build3960558162=/tmp/go-build -gno-record-gcc-switches

What did you do?

I need information about how to use control especially a guide for how to use parameters set variable and more

What did you expect to see?

A gui with parameters or a doc with instructions on it and maybe a features to check if this file contain controlflow or not

What did you see instead?

Nothing maybe the docs which is very good but doesnt help me a lot and im not sure if i doing it correctly

[furax124]

How can I check if this file have control flow ? Maybe it's more simple if you add a flag to it

[lu4p]

You can use -debugdir=debug to check out the generated code.

You can use a disassembler to see how the binary changed.

I don't think there are "official" recommendations for which values make sense you should play around with it.

[furax124]

You can use -debugdir=debug to check out the generated code.

You can use a disassembler to see how the binary changed.

I don't think there are "official" recommendations for which values make sense you should play around with it.

How to I add environment variable ? But thx for your response

[mvdan]

Sorry but we don't provide support. If the docs aren't clear, you can read the code and open a PR to improve them. You can also ask a question in the Q&A discussions page.