Re: [Valgrind-users] RedHat 8.0 pthread "problem"

[Julian S. <js...@ac...>]

On Wednesday 11 June 2003 10:08, Beau D. Simensen wrote:
> > > Now, this works outside of valgrind. Pretty well -- I haven't noticed
> > > any problems with it and other memory debugging stuff seems to think it
> > > is OK [for the most part]. I can actually make it "work" in valgrind,
> > > but only if I have --trace-pthread=all set. However, this dumps far too
> > > much info to be useful for me as I have *alot* of mutex
> > > locking/unlocking.

Sidestepping the discussion about whether threads are actually desirable
here or not ..

Get rid of --trace-pthread=all.  Then it deadlocks again, right?
Now run with --trace-syscalls=yes so we can see what syscall it's
really blocking in.

Also ensure you're using 1.9.6.  There was some ungodly hacking around
I did to try and make non-blocking syscalls really not block, following
RH's more recent glibc hackery, and so V's prior to 1.9.6 may behave
differently.

J