|
From: Eduardo M. <ea...@us...> - 2005-05-09 14:29:31
|
I think glibc 2.3.3 is supported in 2.1.1 valgrind release right?
So, Why am I getting this message here?
is it a problem??
How can I get rid of this message??
In file glibc-2.3.supp, there is no line to support SLES9 glibc-2.3.3
# valgrind --tool=helgrind ./allok
Actual Results:
==13269== Helgrind, a data race detector for x86-linux.
==13269== Copyright (C) 2002-2004, and GNU GPL'd, by Nicholas Nethercote.
==13269== Using valgrind-2.1.1, a program supervision framework for
x86-linux.
==13269== Copyright (C) 2000-2004, and GNU GPL'd, by Julian Seward.
==13269== For more details, rerun with: -v
==13269==
==13269== Thread 2:
==13269== Possible data race writing variable at 0x3F016048
(_rtld_global+72)
==13269== at 0x3F0080C0: _dl_lookup_symbol_x (dl-lookup.c:227)
==13269== by 0x3F00CEEB: fixup (dl-runtime.c:98)
==13269== by 0x3F00CCBF: _dl_runtime_resolve (in /lib/ld-2.3.3.so)
==13269== by 0xB800F58C: do__quit (vg_scheduler.c:1792)
==13269== Address 0x3F016048 is in data section of /lib/ld-2.3.3.so
==13269== Previous state: shared RO, no locks
==13269==
==13269== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 1 from 1)
==13269== 2 possible data races found; 0 lock order problems
alloc.c
#include <pthread.h>
static pthread_mutex_t mx = PTHREAD_MUTEX_INITIALIZER;
static int shared;
static void *th(void *v)
{
pthread_mutex_lock(&mx);
shared++;
pthread_mutex_unlock(&mx);
return 0;
}
int main()
{
pthread_t a, b;
pthread_mutex_lock(&mx);
pthread_mutex_unlock(&mx);
pthread_create(&a, NULL, th, NULL);
pthread_create(&b, NULL, th, NULL);
pthread_join(a, NULL);
pthread_join(b, NULL);
return 0;
}
Regards,
Eduardo A. Munoz
Linux Technology Center
ea...@us...
512-838-8219
|