|
From: Alec O. <Ale...@wb...> - 2006-09-25 21:37:33
|
Howdy folks, Whenever we create a thread while running our linux application through valgrind, we always see the following error when creating a thread: ==24816== Syscall param write(buf) points to uninitialised byte(s) ==24816== at 0x40E7F3B: write (in /lib/libpthread-0.10.so) ==24816== by 0x40E3443: pthread_create@@GLIBC_2.1 (in /lib/libpthread-0.10.so) Is this expected? Do other see this as well? Valgrind 3.2.1 started with: valgrind --tool=memcheck --logfile=vallog --error-limit=no <suppressions file> OS: Linux wbempc 2.4.20-8 #1 Thu Mar 13 17:54:28 EST 2003 i686 i686 i386 GNU/Linux Thank you! Alec ==24816== Memcheck, a memory error detector. ==24816== Copyright (C) 2002-2006, and GNU GPL'd, by Julian Seward et al. ==24816== Using LibVEX rev 1658, a library for dynamic binary translation. ==24816== Copyright (C) 2004-2006, and GNU GPL'd, by OpenWorks LLP. ==24816== Using valgrind-3.2.1, a dynamic binary instrumentation framework. ==24816== Copyright (C) 2000-2006, and GNU GPL'd, by Julian Seward et al. ==24816== For more details, rerun with: -v ==24816== ==24816== My PID = 24816, parent PID = 13461. Prog and args are: ==24816== cwbemserver ==24816== ./cwbemserver.ini ==24816== ==24816== Syscall param write(buf) points to uninitialised byte(s) ==24816== at 0x40E7F3B: write (in /lib/libpthread-0.10.so) ==24816== by 0x40E3443: pthread_create@@GLIBC_2.1 (in /lib/libpthread-0.10.so) ==24816== by 0x459E9FE: startDeliveryThread (httpih.c:407) ==24816== by 0x459F1F7: iha_initialize (httpih.c:719) ==24816== by 0x40CE896: loadAdapterFile (af.c:208) ==24816== by 0x40CEB3B: regIHAAdapterFromFile (af.c:339) ==24816== by 0x40CF0D3: af_startAdapters (af.c:511) ==24816== by 0x406B5E0: wsi_StartCimomNormal (cimom.c:1059) ==24816== by 0x406B87B: wsi_StartCimom (cimom.c:1199) ==24816== by 0x8048A36: main (wsicimom.c:87) ==24816== Address 0xBEFFE2B0 is on thread 1's stack |