[PD] possible threading problem

Charles Henry czhenry at gmail.com
Mon Mar 20 17:10:33 CET 2006


I've been trying valgrind to see what's wrong with my programs in pd. 
Each time I load pd (not the patches) I get the following error:

valgrind --show-below-main=yes --error-limit=no --leak-check=full
--show-reachable=yes /usr/local/bin/pd -r 22050

Is this expected?
Chuck

==6444== Memcheck, a memory error detector for x86-linux.
==6444== Copyright (C) 2002-2005, and GNU GPL'd, by Julian Seward et al.
==6444== Using valgrind-2.4.0, a program supervision framework for x86-linux.
==6444== Copyright (C) 2000-2005, and GNU GPL'd, by Julian Seward et al.
==6444== For more details, rerun with: -v
==6444==
==6444== Conditional jump or move depends on uninitialised value(s)
==6444==    at 0x205BE0: strstr (in /lib/libc-2.3.5.so)
==6444==    by 0x3F36E7: __pthread_initialize_minimal (in
/lib/libpthread-2.3.5.so)
==6444==    by 0x3F3297: (within /lib/libpthread-2.3.5.so)
==6444==    by 0x3F2E7F: (within /lib/libpthread-2.3.5.so)
==6444==    by 0x1B8F1DCA: call_init (in /lib/ld-2.3.5.so)
==6444==    by 0x1B8F1EEC: _dl_init (in /lib/ld-2.3.5.so)
==6444==    by 0x1B8E47CE: (within /lib/ld-2.3.5.so)
==6444==
==6444== Conditional jump or move depends on uninitialised value(s)
==6444==    at 0x205BE4: strstr (in /lib/libc-2.3.5.so)
==6444==    by 0x3F36E7: __pthread_initialize_minimal (in
/lib/libpthread-2.3.5.so)
==6444==    by 0x3F3297: (within /lib/libpthread-2.3.5.so)
==6444==    by 0x3F2E7F: (within /lib/libpthread-2.3.5.so)
==6444==    by 0x1B8F1DCA: call_init (in /lib/ld-2.3.5.so)
==6444==    by 0x1B8F1EEC: _dl_init (in /lib/ld-2.3.5.so)
==6444==    by 0x1B8E47CE: (within /lib/ld-2.3.5.so)




More information about the Pd-list mailing list