DRD regtest: don't use -q with tc22_exit_w_lock

This seems a better fix than turning off Darwin aysync signal
termination messages.

Also I don't think that the 32bit variant is used any more.

diff --git a/drd/tests/tc22_exit_w_lock.stderr.exp-64bit b/drd/tests/tc22_exit_w_lock.stderr.exp-64bit
index 03e8046506705f16f17e9a72953b90e2a45ebcf3..ce55c062b87d1455374c38bb25d99d406dbb1537 100644 (file)
--- a/drd/tests/tc22_exit_w_lock.stderr.exp-64bit
+++ b/drd/tests/tc22_exit_w_lock.stderr.exp-64bit
@@ -1,3 +1,4 @@
+
 Mutex still locked at thread exit: mutex 0x........, recursion count 1, owner 3.
    at 0x........: pthread_join (drd_pthread_intercepts.c:?)
    by 0x........: main (tc22_exit_w_lock.c:43)
@@ -6,3 +7,9 @@ mutex 0x........ was first observed at:
    by 0x........: child_fn1 (tc22_exit_w_lock.c:18)
    by 0x........: vgDrd_thread_wrapper (drd_pthread_intercepts.c:?)
 
+
+Process terminating with default action of signal 6 (SIGABRT)
+   at 0x........: kill (in /...libc...)
+   by 0x........: main (tc22_exit_w_lock.c:48)
+
+ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)

diff --git a/drd/tests/tc22_exit_w_lock.vgtest b/drd/tests/tc22_exit_w_lock.vgtest
index 5edf4e5ffe6129b18111e5650aea9acc0b3a0bf4..023fea0e075e927a48cb5199c8ca3033c25204dd 100644 (file)
--- a/drd/tests/tc22_exit_w_lock.vgtest
+++ b/drd/tests/tc22_exit_w_lock.vgtest
@@ -1,4 +1,4 @@
 prereq: ./supported_libpthread && [ -e ../../helgrind/tests/tc22_exit_w_lock ]
-vgopts: --num-callers=3 -q
+vgopts: --num-callers=3
 prog: ../../helgrind/tests/tc22_exit_w_lock
 cleanup: rm -f vgcore.*