From c0bc4707ab8096085eff1ec015a890a2ec66929c Mon Sep 17 00:00:00 2001 From: Christopher Wellons Date: Tue, 2 May 2023 18:22:55 -0400 Subject: [PATCH] Update README.md note about UBSan for GCC >= 13 The new option name is a lot nicer, so encourage its use! I don't know if the old option will ever be removed. --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 5ea35d3..d6adca8 100644 --- a/README.md +++ b/README.md @@ -176,8 +176,8 @@ quite support cross-compilation. A decent alternative would be Neither Address Sanitizer (ASan) nor Thread Sanitizer (TSan) [has been ported to Mingw-w64][san] ([also][san2]), but Undefined Behavior Sanitizer (UBSan) works perfectly under GDB. With both `-fsanitize=undefined` and -`-fsanitize-undefined-trap-on-error`, GDB will [break precisely][break] on -undefined behavior, and it does not require linking with libsanitizer. +`-fsanitize-trap`, GDB will [break precisely][break] on undefined +behavior, and it does not require linking with libsanitizer. The kit includes a unique [`debugbreak` command][debugbreak]. It causes all debugee processes to break in the debugger, like using Windows' F12