New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

go-fuzz-build: generate an executable rather than a zip file #277

Open

josharian opened this issue Oct 11, 2019 · 0 comments

Collaborator

josharian commented Oct 11, 2019

[broken out from discussion in #273]

It'd be better to do as std does with testing and emit an executable instead of a zip file and using an external runner.

Off the top of my head, steps for this:

figure out how to have instrumented code live alongside regular code (test runner)
make sonar instrumentation always present and controlled on a run by run basis
do dynamic rather than static literal collection
refactor everything to support this

I don't know how to do step one. The rest are non-trivial, but seem possible.

josharian mentioned this issue

all: add basic version skew detection #273

Open

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment