mirror of
https://github.com/morgan9e/systemd
synced 2026-04-14 16:37:19 +09:00
2614d83aa0
By default, UBSan neither crashes nor exits with a non-zero exit code when undefined behavior has been detected. This is problematic because it makes it much harder to catch issues like https://github.com/systemd/systemd/issues/10346, https://github.com/systemd/systemd/issues/10347, and https://github.com/systemd/systemd/issues/10333. In fact, those issue were found just because I decided to grep the test log, which isn't something that I normally do :-) As it turns out, the only way to make UBSan signal that something is wrong that works more or less reliably everywhere is to pass halt_on_error=1 (though, it's probably worth noting that it's currently not set for PID1 in order not to trigger kernel panics). See https://reviews.llvm.org/D35085#804183 and https://chromium.googlesource.com/chromium/src/testing/libfuzzer/+/HEAD/reference.md
systemd - System and Service Manager
Details
General information about systemd can be found in the systemd Wiki.
Information about build requirements are provided in the README file.
Consult our NEWS file for information about what's new in the most recent systemd versions.
Please see the HACKING file for information how to hack on systemd and test your modifications.
Please see our Contribution Guidelines for more information about filing GitHub Issues and posting GitHub Pull Requests.
When preparing patches for systemd, please follow our Coding Style Guidelines.
If you are looking for support, please contact our mailing list or join our IRC channel.
Stable branches with backported patches are available in the stable repo.