|
From: David F. <df...@qu...> - 2004-08-03 00:20:25
|
Tom Hughes <thh <at> cyberscience.com> writes: > > In message <6805AEBFF646BD4FB58D21469872D8767EE6D0 <at> NAEX02.na.qualcomm.com> > "Fernandez, Dave" <dfern <at> qualcomm.com> wrote: > > > I tried building valgrind with different values in in > > coregrind/vg_include.h up to 25000 and still get the same error. > > Any ideas what the right value should be and how to circumvent this > > problem? > > That seems awfully large - what would you expect to be the > maximum number of read-write locks created by your application? > > Tom > I agree the number is quite large but I started with 100, 1000,10000 and so on and I still get the same error. The application starts to come up but then valgrind aborts right after printing the VG_N_RWLOCKS error. My application should not require more than 200 RW locks and maybe that's still high but is a good estimate. I'm trying with valgrind 2.1.2 Even when running valgrind with -v I don't see any meaningful debug info to know what might be wrong. Any suggestions on how to keep valgrind happy? Thanks, DF |