Author: sewardj
Date: 2007-11-01 17:59:40 +0000 (Thu, 01 Nov 2007)
New Revision: 7077
Log:
Update expected output following r7075.
Modified:
branches/THRCHECK/thrcheck/tests/tc20_verifywrap.stderr.exp-glibc25-amd64
Modified:
branches/THRCHECK/thrcheck/tests/tc20_verifywrap.stderr.exp-glibc25-amd64
===================================================================
--- branches/THRCHECK/thrcheck/tests/tc20_verifywrap.stderr.exp-glibc25-amd64
2007-11-01 17:15:35 UTC (rev 7076)
+++ branches/THRCHECK/thrcheck/tests/tc20_verifywrap.stderr.exp-glibc25-amd64
2007-11-01 17:59:40 UTC (rev 7077)
@@ -1,5 +1,8 @@
+
+------ This is output for >= glibc 2.4 ------
+
---------------- pthread_create/join ----------------
Thread #1 is the program's root thread
@@ -9,10 +12,10 @@
by 0x........: ...
by 0x........: [EMAIL PROTECTED] (in /lib/libpthread...)
by 0x........: [EMAIL PROTECTED] (tc_intercepts.c:...)
- by 0x........: main (tc20_verifywrap.c:64)
+ by 0x........: main (tc20_verifywrap.c:76)
Possible data race during write of size 2 at 0x........
- at 0x........: main (tc20_verifywrap.c:66)
+ at 0x........: main (tc20_verifywrap.c:78)
Old state: owned exclusively by thread #2
New state: shared-modified by threads #1, #2
Reason: this thread, #1, holds no locks at all
@@ -20,7 +23,7 @@
Thread #1's call to pthread_join failed
with error code 35 (EDEADLK: Resource deadlock would occur)
at 0x........: pthread_join (tc_intercepts.c:...)
- by 0x........: main (tc20_verifywrap.c:71)
+ by 0x........: main (tc20_verifywrap.c:83)
---------------- pthread_mutex_lock et al ----------------
@@ -28,55 +31,55 @@
Thread #1's call to pthread_mutex_init failed
with error code 95 (EOPNOTSUPP: Operation not supported on transport
endpoint)
at 0x........: pthread_mutex_init (tc_intercepts.c:...)
- by 0x........: main (tc20_verifywrap.c:80)
+ by 0x........: main (tc20_verifywrap.c:92)
Thread #1: pthread_mutex_destroy of a locked mutex
at 0x........: pthread_mutex_destroy (tc_intercepts.c:...)
- by 0x........: main (tc20_verifywrap.c:85)
+ by 0x........: main (tc20_verifywrap.c:102)
Thread #1's call to pthread_mutex_destroy failed
with error code 16 (EBUSY: Device or resource busy)
at 0x........: pthread_mutex_destroy (tc_intercepts.c:...)
- by 0x........: main (tc20_verifywrap.c:85)
+ by 0x........: main (tc20_verifywrap.c:102)
Thread #1's call to pthread_mutex_lock failed
with error code 22 (EINVAL: Invalid argument)
at 0x........: pthread_mutex_lock (tc_intercepts.c:...)
- by 0x........: main (tc20_verifywrap.c:89)
+ by 0x........: main (tc20_verifywrap.c:108)
Thread #1's call to pthread_mutex_trylock failed
with error code 22 (EINVAL: Invalid argument)
at 0x........: pthread_mutex_trylock (tc_intercepts.c:...)
- by 0x........: main (tc20_verifywrap.c:93)
+ by 0x........: main (tc20_verifywrap.c:116)
Thread #1's call to pthread_mutex_timedlock failed
with error code 22 (EINVAL: Invalid argument)
at 0x........: pthread_mutex_timedlock (tc_intercepts.c:...)
- by 0x........: main (tc20_verifywrap.c:98)
+ by 0x........: main (tc20_verifywrap.c:121)
Thread #1 unlocked an invalid lock at 0x........
at 0x........: pthread_mutex_unlock (tc_intercepts.c:...)
- by 0x........: main (tc20_verifywrap.c:102)
+ by 0x........: main (tc20_verifywrap.c:125)
Thread #1's call to pthread_mutex_unlock failed
with error code 22 (EINVAL: Invalid argument)
at 0x........: pthread_mutex_unlock (tc_intercepts.c:...)
- by 0x........: main (tc20_verifywrap.c:102)
+ by 0x........: main (tc20_verifywrap.c:125)
---------------- pthread_cond_wait et al ----------------
Thread #1 unlocked a not-locked lock at 0x........
at 0x........: [EMAIL PROTECTED] (tc_intercepts.c:...)
- by 0x........: main (tc20_verifywrap.c:119)
+ by 0x........: main (tc20_verifywrap.c:147)
Lock at 0x........ was first observed
at 0x........: pthread_mutex_init (tc_intercepts.c:...)
- by 0x........: main (tc20_verifywrap.c:117)
+ by 0x........: main (tc20_verifywrap.c:145)
Thread #1's call to pthread_cond_wait failed
with error code 1 (EPERM: Operation not permitted)
at 0x........: [EMAIL PROTECTED] (tc_intercepts.c:...)
- by 0x........: main (tc20_verifywrap.c:119)
+ by 0x........: main (tc20_verifywrap.c:147)
FIXME: can't figure out how to verify wrap of pthread_cond_signal
@@ -87,27 +90,27 @@
Thread #1's call to pthread_cond_timedwait failed
with error code 22 (EINVAL: Invalid argument)
at 0x........: [EMAIL PROTECTED] (tc_intercepts.c:...)
- by 0x........: main (tc20_verifywrap.c:137)
+ by 0x........: main (tc20_verifywrap.c:165)
---------------- pthread_rwlock_* ----------------
Thread #1 unlocked a not-locked lock at 0x........
at 0x........: pthread_rwlock_unlock (tc_intercepts.c:...)
- by 0x........: main (tc20_verifywrap.c:151)
+ by 0x........: main (tc20_verifywrap.c:179)
Lock at 0x........ was first observed
at 0x........: pthread_rwlock_init (tc_intercepts.c:...)
- by 0x........: main (tc20_verifywrap.c:150)
+ by 0x........: main (tc20_verifywrap.c:178)
(1) no error on next line
(2) no error on next line
(3) ERROR on next line
Thread #1 unlocked a not-locked lock at 0x........
at 0x........: pthread_rwlock_unlock (tc_intercepts.c:...)
- by 0x........: main (tc20_verifywrap.c:168)
+ by 0x........: main (tc20_verifywrap.c:196)
Lock at 0x........ was first observed
at 0x........: pthread_rwlock_init (tc_intercepts.c:...)
- by 0x........: main (tc20_verifywrap.c:158)
+ by 0x........: main (tc20_verifywrap.c:186)
(4) no error on next line
(5) no error on next line
(6) no error on next line
@@ -116,10 +119,10 @@
Thread #1 unlocked a not-locked lock at 0x........
at 0x........: pthread_rwlock_unlock (tc_intercepts.c:...)
- by 0x........: main (tc20_verifywrap.c:184)
+ by 0x........: main (tc20_verifywrap.c:212)
Lock at 0x........ was first observed
at 0x........: pthread_rwlock_init (tc_intercepts.c:...)
- by 0x........: main (tc20_verifywrap.c:158)
+ by 0x........: main (tc20_verifywrap.c:186)
---------------- sem_* ----------------
@@ -127,7 +130,7 @@
Thread #1's call to sem_init failed
with error code 22 (EINVAL: Invalid argument)
at 0x........: [EMAIL PROTECTED] (tc_intercepts.c:...)
- by 0x........: main (tc20_verifywrap.c:200)
+ by 0x........: main (tc20_verifywrap.c:228)
FIXME: can't figure out how to verify wrap of sem_destroy
@@ -135,7 +138,7 @@
Thread #1: Bug in libpthread: sem_wait succeeded on semaphore without prior
sem_post
at 0x........: sem_wait_WRK (tc_intercepts.c:...)
by 0x........: sem_wait (tc_intercepts.c:...)
- by 0x........: main (tc20_verifywrap.c:214)
+ by 0x........: main (tc20_verifywrap.c:242)
FIXME: can't figure out how to verify wrap of sem_post
@@ -144,15 +147,15 @@
Thread #1 deallocated location 0x........ containing a locked lock
- at 0x........: main (tc20_verifywrap.c:235)
+ at 0x........: main (tc20_verifywrap.c:263)
Lock at 0x........ was first observed
at 0x........: pthread_rwlock_init (tc_intercepts.c:...)
- by 0x........: main (tc20_verifywrap.c:188)
+ by 0x........: main (tc20_verifywrap.c:216)
Thread #1 deallocated location 0x........ containing a locked lock
- at 0x........: main (tc20_verifywrap.c:235)
+ at 0x........: main (tc20_verifywrap.c:263)
Lock at 0x........ was first observed
at 0x........: pthread_mutex_init (tc_intercepts.c:...)
- by 0x........: main (tc20_verifywrap.c:117)
+ by 0x........: main (tc20_verifywrap.c:145)
ERROR SUMMARY: 20 errors from 20 contexts (suppressed: 0 from 0)
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Valgrind-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/valgrind-developers
