11:00:35.812 INFO GlslGenerate - About to generate 5 shader families, each with 1 variant.
11:00:35.814 INFO GlslGenerate - Generating family 0 from reference bubblesort_flag.json.
11:00:35.838 INFO ExecHelper - ~/graphicsfuzz/graphicsfuzz/target/graphicsfuzz/bin/Linux/glslangValidator -E --stdin -S frag
11:00:35.868 INFO ExecHelper - Result: 0
11:00:36.168 INFO ExecHelper - ~/graphicsfuzz/graphicsfuzz/target/graphicsfuzz/bin/Linux/glslangValidator -E --stdin -S frag
11:00:36.192 INFO ExecHelper - Result: 0
11:00:36.450 INFO ExecHelper - ~/graphicsfuzz/graphicsfuzz/target/graphicsfuzz/bin/Linux/glslangValidator -E --stdin -S frag
Indicating that validator is indeed being run.
For my use case, running the validator isn't important since it isn't much more expensive to pass the shader to the binary I'm trying to find memory corruption in.
On HEAD on dev branch, it appears that disable-glslangValidator isn't working as I expect (maybe I misunderstand what it should do).
When I run:
I see the following output
Indicating that validator is indeed being run.
For my use case, running the validator isn't important since it isn't much more expensive to pass the shader to the binary I'm trying to find memory corruption in.