Marc Herbert abad20650a .github: ipc_fuzzer: upload stdout logs ... Quoting @andyross in https://github.com/thesofproject/sof/pull/7668#issuecomment-1561587959 > OK, as it turns out when running native_posix+fuzzing, the fuzzer > output goes to stderr (and appears here) where the console output goes > to stdout, and is currently being discarded. For a sanitizer-detected > failure, that's actually fine as the stack trace will show up in the > CI logs. But this was just a call to posix_exit(), which is an "error" > to the fuzzer but not very informative to us without knowing the > software state that led to it. Most likely this is a Zephyr > panic (e.g. an assertion failure -- not a trap like SIGSEGV/SIGILL > that would be caught by the host OS and thus libfuzzer), because the > default fatal error handler is to tell the arch layer to do a system > halt, and native_posix implements this by exiting. And it's certainly > not unlikely to have been triggered by the fuzzing. > Basically: @marc-hb if we could arrange to save the stdout of the > offending fuzz process on failure that would be great. Alas this > particular incident may have been lost, but there will surely be more. Signed-off-by: Marc Herbert <marc.herbert@intel.com>		2023-05-29 09:59:34 +03:00
..
ISSUE_TEMPLATE	github: fix link to bug tracking docs	2020-01-09 11:24:06 +00:00
workflows	.github: ipc_fuzzer: upload stdout logs	2023-05-29 09:59:34 +03:00