Add test for #13690 fuzzing crash (assert) in ErrorMessage::setmsg()

[chrchr-github]

No description provided.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[firewave]

FAILED test/cli/fuzz_test.py::test_fuzz_crash - AssertionError: assert {'crash-6d019f821f348d758d8d88bd7de692af6f9b07f4': ''} == {}
  
  Left contains 1 more item:
  {'crash-6d019f821f348d758d8d88bd7de692af6f9b07f4': ''}
  
  Full diff:
  - {}
  + {
  +     'crash-6d019f821f348d758d8d88bd7de692af6f9b07f4': '',
  + }

We need to store more information on how it failed.

failures[f] = stdout

That should possibly be stdout if stdout else stderr to hopefully get more information.

[chrchr-github]

The assert also doesn't fire on Windows apparently.

[firewave]

The assert also doesn't fire on Windows apparently.

We only run it with a Release build and that has NDEBUG (explicitly) set and thus no asserts are generated. See also https://trac.cppcheck.net/ticket/10736.

[chrchr-github]

The assert also doesn't fire on Windows apparently.

We only run it with a Release build and that has NDEBUG (explicitly) set and thus no asserts are generated. See also https://trac.cppcheck.net/ticket/10736.

Yeah, that's in the CI. But I can't reproduce it locally in Debug mode either.

[firewave]

Yeah, that's in the CI. But I can't reproduce it locally in Debug mode either.

Most likely related to differences in newline handling.

[chrchr-github]

Yeah, that's in the CI. But I can't reproduce it locally in Debug mode either.

Most likely related to differences in newline handling.

Yes, the example has a 0xaat the end. But the issue needs to be fixed in simplecpp.