vitalybuka wrote: If you don't mind to cover here or in next patch: ``` AddressSanitizer ThreadSanitizer MemorySanitizer UndefinedBehaviorSanitizer DataFlowSanitizer LeakSanitizer TypeSanitizer RealtimeSanitizer SanitizerCoverage ```
Also CFI: > Trapping and Diagnostics: > By default, CFI will abort the program immediately upon detecting a control > flow integrity violation. You can use the -> fno-sanitize-trap= flag to cause > CFI to print a diagnostic similar to the one below before the program aborts. CFI in diagnostics mode is essencially UBSAN. I would just say for diagnostics options refer to UndefinedBehaviorSanitizer docs https://github.com/llvm/llvm-project/pull/218793 _______________________________________________ cfe-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
