Hi, Dear Valgrind Developers! I'm on my way to make threaded version of Firebird to work under Valgrind. Here is my problem. ------------------------------------------------------------------------ -------------------------- =3D=3D6492=3D=3D Memcheck, a memory error detector for x86-linux. =3D=3D6492=3D=3D Copyright (C) 2002-2004, and GNU GPL'd, by Julian = Seward et al. =3D=3D6492=3D=3D Using valgrind-2.1.2, a program supervision framework = for x86-linux. =3D=3D6492=3D=3D Copyright (C) 2000-2004, and GNU GPL'd, by Julian = Seward et al. =3D=3D6492=3D=3D For more details, rerun with: -v =3D=3D6492=3D=3D =3D=3D6492=3D=3D valgrind's libpthread.so: UNIMPLEMENTED FUNCTION: pthread_rwlockattr_setkind_np =3D=3D6492=3D=3D valgrind's libpthread.so: unimplemented function Please report this bug at: valgrind.kde.org ------------------------------------------------------------------------ -------------------------- The convern I have that people using very fresh Firebird client may have problems using Valgrind to debug their applications. They of course may apply some of the Valgrind patches floating around such as http://people.redhat.com/graydon/02-valgrind-pthread-api.patch but it would be nice to see this feature in main Valgrind tree. Since pthread_rwlockattr_setkind_np options are mostly performance optimizations stubbed implementation should work fine. We use PTHREAD_RWLOCK_PREFER_WRITER_NONRECURSIVE_NP if it is available. Nickolay Samofatov |