Menu
▾
▴
[Valgrind-developers] [valgrind] Remove unused helgrind expected
|
From: Paul F. <pa...@so...> - 2023-02-28 20:54:21
|
https://sourceware.org/git/gitweb.cgi?p=valgrind.git;h=189ea2bf9efe066b72b2a1b885b4631b4f29c4b8 commit 189ea2bf9efe066b72b2a1b885b4631b4f29c4b8 Author: Paul Floyd <pj...@wa...> Date: Tue Feb 28 21:52:54 2023 +0100 Remove unused helgrind expected I don't think that this can match any more. Diff: --- helgrind/tests/Makefile.am | 3 +- helgrind/tests/pth_destroy_cond.stderr.exp2 | 44 ----------------------------- 2 files changed, 1 insertion(+), 46 deletions(-) diff --git a/helgrind/tests/Makefile.am b/helgrind/tests/Makefile.am index 65f18f1435..5338ea4d6d 100755 --- a/helgrind/tests/Makefile.am +++ b/helgrind/tests/Makefile.am @@ -59,8 +59,7 @@ EXTRA_DIST = \ pth_barrier2.vgtest pth_barrier2.stdout.exp pth_barrier2.stderr.exp \ pth_barrier3.vgtest pth_barrier3.stdout.exp pth_barrier3.stderr.exp \ pth_destroy_cond.vgtest \ - pth_destroy_cond.stdout.exp \ - pth_destroy_cond.stderr.exp pth_destroy_cond.stderr.exp2 \ + pth_destroy_cond.stdout.exp pth_destroy_cond.stderr.exp \ pth_cond_destroy_busy.vgtest pth_cond_destroy_busy.stderr.exp \ pth_cond_destroy_busy.stderr.exp-ppc64 \ pth_cond_destroy_busy.stderr.exp-solaris \ diff --git a/helgrind/tests/pth_destroy_cond.stderr.exp2 b/helgrind/tests/pth_destroy_cond.stderr.exp2 deleted file mode 100644 index 593b4ef35b..0000000000 --- a/helgrind/tests/pth_destroy_cond.stderr.exp2 +++ /dev/null @@ -1,44 +0,0 @@ ----Thread-Announcement------------------------------------------ - -Thread #x was created - ... - by 0x........: pthread_create@* (hg_intercepts.c:...) - by 0x........: main (pth_destroy_cond.c:29) - ----Thread-Announcement------------------------------------------ - -Thread #x is the program's root thread - ----------------------------------------------------------------- - - Lock at 0x........ was first observed - at 0x........: pthread_mutex_init (hg_intercepts.c:...) - by 0x........: main (pth_destroy_cond.c:25) - Address 0x........ is 0 bytes inside data symbol "mutex" - -Possible data race during read of size 1 at 0x........ by thread #x -Locks held: 1, at address 0x........ - at 0x........: my_memcmp (hg_intercepts.c:...) - by 0x........: pthread_cond_destroy_WRK (hg_intercepts.c:...) - by 0x........: pthread_cond_destroy@* (hg_intercepts.c:...) - by 0x........: ThreadFunction (pth_destroy_cond.c:18) - by 0x........: mythread_wrapper (hg_intercepts.c:...) - ... - -This conflicts with a previous write of size 4 by thread #x -Locks held: none - ... - by 0x........: pthread_cond_wait_WRK (hg_intercepts.c:...) - by 0x........: pthread_cond_wait@* (hg_intercepts.c:...) - by 0x........: main (pth_destroy_cond.c:31) - Address 0x........ is 4 bytes inside data symbol "cond" - ----------------------------------------------------------------- - -Thread #x: pthread_cond_destroy: destruction of condition variable being waited upon - at 0x........: pthread_cond_destroy_WRK (hg_intercepts.c:...) - by 0x........: pthread_cond_destroy@* (hg_intercepts.c:...) - by 0x........: ThreadFunction (pth_destroy_cond.c:18) - by 0x........: mythread_wrapper (hg_intercepts.c:...) - ... - |
