Blair Zajac blair@orcaware.com writes:
Do you get simple errors like these? I'm on RedHat 8.0
No, I see very occasional errors when BDB 4.0 writes unitialized
memory to its log file. I'm using Debian/stable with valgrind 1.0.4
built from Debian/unstable source.
% valgrind svn --version
==23319== Memcheck, a.k.a. Valgrind, a memory error detector for x86-linux.
==23319== Copyright (C) 2002, and GNU GPL'd, by Julian Seward.
==23319== Using valgrind-1.9.3, a program instrumentation system for x86-linux.
==23319== Copyright (C) 2000-2002, and GNU GPL'd, by Julian Seward.
==23319== Estimated CPU clock rate is 349 MHz
==23319== For more details, rerun with: -v
==23319==
==23319== pthread_mutex_unlock: mutex is not locked
==23319== at 0x4067FA0E: __pthread_mutex_unlock (vg_libpthread.c:986)
==23319== by 0x42062577: _IO_fclose@@GLIBC_2.1 (in /lib/i686/libc-2.2.93.so)
==23319== by 0x420EA7F8: nss_parse_file (in /lib/i686/libc-2.2.93.so)
==23319== by 0x420EA3C9: __GI___nss_database_lookup (in /lib/i686/libc-2.2.93.so)
[snip]
It's not too easy to debug when you have errors like these on
the most simple of commands.
Add them to valgrind's supression files and you won't see them. The
Debian package adds a number of suppressions beyond those provided by
upstream. For example
#-------- Threading bugs?
{
pthread_error/__pthread_mutex_destroy/__closedir
PThread
fun:pthread_error
fun:__pthread_mutex_destroy
fun:__closedir
}
{
pthread_error/__pthread_mutex_destroy/_IO_default_finish
PThread
fun:pthread_error
fun:__pthread_mutex_destroy
fun:_IO_default_finish*
}
{
__pthread_mutex_unlock/_IO_funlockfile
PThread
fun:__pthread_mutex_unlock
fun:_IO_funlockfile
}
{
__pthread_mutex_unlock/__register_frame_info
PThread
fun:__pthread_mutex_unlock
fun:__register_frame_info
}
--
Philip Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 14 02:05:45 2006