[compiler-rt] b983431 - [rtsan] Fix issue when intercepted function was not execve in test (#144018)
via llvm-commits
llvm-commits at lists.llvm.org
Sun Jun 15 06:55:26 PDT 2025
Author: Chris Apple
Date: 2025-06-15T06:55:22-07:00
New Revision: b983431c281a0acb9e446c7c9d72474f4d09e8e0
URL: https://github.com/llvm/llvm-project/commit/b983431c281a0acb9e446c7c9d72474f4d09e8e0
DIFF: https://github.com/llvm/llvm-project/commit/b983431c281a0acb9e446c7c9d72474f4d09e8e0.diff
LOG: [rtsan] Fix issue when intercepted function was not execve in test (#144018)
Added:
Modified:
compiler-rt/test/rtsan/fork_exec.cpp
Removed:
################################################################################
diff --git a/compiler-rt/test/rtsan/fork_exec.cpp b/compiler-rt/test/rtsan/fork_exec.cpp
index 3b2d2e5ca2f5d..5890a0936a2f7 100644
--- a/compiler-rt/test/rtsan/fork_exec.cpp
+++ b/compiler-rt/test/rtsan/fork_exec.cpp
@@ -45,7 +45,12 @@ int main() MAYBE_NONBLOCKING {
}
// CHECK-NOHALT: Intercepted call to {{.*}} `fork` {{.*}}
-// CHECK-NOHALT: Intercepted call to {{.*}} `execve` {{.*}}
+
+// We should also get some other intercepted call. On some systems this
+// is `execve`, on others, it's a lock to set up `execve`. In either
+// case, just check that we get a second intercepted call, don't sweat
+// the name.
+// CHECK-NOHALT: Intercepted call to {{.*}}
// usleep checks that rtsan is still enabled in the parent process
// See note in our interceptors file for why we don't look for `wait`
More information about the llvm-commits
mailing list