Comment #2 on issue 40330 by da...@adalogics.com: binutils:fuzz_as: Stack-use-after-return in as_bad_internal https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=40330#c2
Thanks for the analysis. I see two approaches forward, either come up with some solution in the fuzzer that resets all of the variables, or disabling the check for stack-use-after-return in the fuzzer. I propose we disable it for now so the fuzzer is not blocked by these checks, and then perhaps change the fuzzer to reset all of the variables at a later stage. Does that sound reasonable to you Alan? -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment.
