From 42f79776cd00602c3e03085e729cb003a3da7c32 Mon Sep 17 00:00:00 2001 From: Emily Deng Date: Thu, 6 Mar 2025 17:08:34 +0800 Subject: [PATCH] kfdtest: Fix the childStatus is 0x7f error for KFDDBGTest.HitMemoryViolation For the case parent goes faster then child, and child hasn't call the second raise(SIGSTOP), then parent's "waitpid(childPid, &childStatus, 0)" will return, and the childStatus will be 0x137f, which is SIGSTOP signal id. Signed-off-by: Emily Deng --- libhsakmt/tests/kfdtest/src/KFDDBGTest.cpp | 3 +++ 1 file changed, 3 insertions(+) diff --git a/libhsakmt/tests/kfdtest/src/KFDDBGTest.cpp b/libhsakmt/tests/kfdtest/src/KFDDBGTest.cpp index 940f0d8e21..ab19dddc33 100644 --- a/libhsakmt/tests/kfdtest/src/KFDDBGTest.cpp +++ b/libhsakmt/tests/kfdtest/src/KFDDBGTest.cpp @@ -599,6 +599,9 @@ TEST_F(KFDDBGTest, HitMemoryViolation) { break; } } + waitpid(childPid, &childStatus, 0); + while (!WIFSTOPPED(childStatus)); + // Assume tracee queue has died and halted process ptrace(PTRACE_CONT, childPid, NULL, NULL);