custom-crash-state: s looks truncated. Oliver, can you move this line to start of stacktrace so that it is not truncated.

Detailed report: https://cluster-fuzz.appspot.com/testcase?key=6000655982657536

Fuzzer: libfuzzer_base_json_reader_fuzzer
Job Type: libfuzzer_chrome_msan
Platform Id: linux

Crash Type: Hang
Crash Address: 
Crash State:
  NULL

Unminimized Testcase: https://cluster-fuzz.appspot.com/download/AMIfv942T5gLB0swWlLnu9ap47c8Re1cLCUVUUUTlfo4D1vS4Yn4pXxg8OctBYfrqjvzwYoBVG1ZDAwFtlYZqih16MhRFaj9q1APxM0gDPpYZznoU3f27K-JKOLBDI4KjX2QOOTTZeoGdG5OzWnpkS02ZDznNDHMmg?testcase_id=6000655982657536


Filer: inferno

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md for more information.

See also #2, i think some stats are truncated too. since we just rely on stacktrace END_MARKER which would be SUMMARY: line. 

I think AFL will be impacted as well. so, i think we just should do both custom state and stats before crash stacktrace (less than ideal, but can't think of any other ideas). CF relies on finishing early as soon as it sees stack end marker, so that is by design.

Truncated stats in the output shouldn't matter, as they are processed in the launcher script and not used by CF. That said, we'll have to make sure that the processing happens before CF kills the launcher. 

https://chromereviews.googleplex.com/464297013/ should address this for libFuzzer.

Thanks Oliver for fixing libFuzzer.

Jonathan, can you fix this for AFL.

Fixed by https://chromereviews.googleplex.com/472187013/#ps1

Removing EditIssue view restrictions from ClusterFuzz filed bugs. If you believe that this issue should still be restricted, please reapply the label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot