[all-commits] [llvm/llvm-project] d26510: Augment `uncaught-exception.test` fuzzer test to b...

[David Justo via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: d265105b8f50718a684d792d3ca957231d668533
      https://github.com/llvm/llvm-project/commit/d265105b8f50718a684d792d3ca957231d668533
  Author: David Justo <david.justo.1996 at gmail.com>
  Date:   2025-06-18 (Wed, 18 Jun 2025)

  Changed paths:
    M compiler-rt/test/fuzzer/uncaught-exception.test

  Log Message:
  -----------
  Augment `uncaught-exception.test` fuzzer test to be msvc-compatible (#125924)

Today, the `uncaught-exception.test` fuzzer test checks for the string
"libFuzzer: deadly signal" in the program output as the result of an
uncaught exception.

Although this is correct for `clang`, `msvc` reports a different error
message: "libFuzzer: uncaught C++ exception". Since `msvc` reuses the
`libFuzzer` infrastructure for ASan regression testing, it would help us
greatly if the test handled the `msvc` divergence more gracefully.

**This PR:** augments this test so check for a different string (namely
"libFuzzer: uncaught C++ exception") if the compiler target matches the
`msvc` naming scheme.

I understand if this is outside the scope of support for LLVM as well,
and I'm also open for different approaches here. Thanks!



To unsubscribe from these emails, change your notification settings at https://github.com/llvm/llvm-project/settings/notifications