ftmemsim-valgrind/drd/tests/bar_bad.stderr.exp
Mark Wielaard 5f37e4dcde Workaround bar_bad testcase hanging with newer glibc in helgrind/drd tests.
This is a workaround for bug #358213 helgrind/drd pthread_barrier tests
hangs with new glibc pthread barrier implementation. This makes sure that
the tests don't hang anymore. It does this by creating new threads that
sleep and kill the other threads after some time. But this introduces
some non-determinism that might cause the tests to occassionally fail
(both against old and new glibc implementations).

git-svn-id: svn://svn.valgrind.org/valgrind/trunk@15962
2016-09-19 14:16:35 +00:00

39 lines
1.3 KiB
Plaintext

initialise a barrier with zero count
pthread_barrier_init: 'count' argument is zero: barrier 0x........
at 0x........: pthread_barrier_init (drd_pthread_intercepts.c:?)
by 0x........: main (bar_bad.c:?)
initialise a barrier twice
Barrier reinitialization: barrier 0x........
at 0x........: pthread_barrier_init (drd_pthread_intercepts.c:?)
by 0x........: main (bar_bad.c:?)
barrier 0x........ was first observed at:
at 0x........: pthread_barrier_init (drd_pthread_intercepts.c:?)
by 0x........: main (bar_bad.c:?)
initialise a barrier which has threads waiting on it
Barrier reinitialization: barrier 0x........
at 0x........: pthread_barrier_init (drd_pthread_intercepts.c:?)
by 0x........: main (bar_bad.c:?)
barrier 0x........ was first observed at:
at 0x........: pthread_barrier_init (drd_pthread_intercepts.c:?)
by 0x........: main (bar_bad.c:?)
destroy a barrier that has waiting threads
Destruction of a barrier with active waiters: barrier 0x........
at 0x........: pthread_barrier_destroy (drd_pthread_intercepts.c:?)
by 0x........: main (bar_bad.c:?)
barrier 0x........ was first observed at:
at 0x........: pthread_barrier_init (drd_pthread_intercepts.c:?)
by 0x........: main (bar_bad.c:?)
destroy a barrier that was never initialised
ERROR SUMMARY: 5 errors from 4 contexts (suppressed: 0 from 0)