Hey, * Mathias Fröhlich -- Tuesday 10 February 2009: > I can see no connection between the helgrind warning and a segfault. > What helgrind tells you, is that there is a possible dealock situation > that can potentially happen due to that inverted lock order. > But the effect of a deadlock is a hanging application or thread or > something like that - not a segfault ...
Yes, that's what I even assumed. I was surprised to get a segfault on the lock. But then again, a segfault on the lock, a reported threading error there, ... and lack of knowledge about threading. ;-) * Mathias Fröhlich -- Tuesday 10 February 2009: > For the nvidia drivers on linux you need the --smc-check=all valgrind > argument. The thing appears to be that the nvidia drivers dynamically build > code on the cpu that is not tracked correctly by valgrind without that > argument Oh, that's news to me. Thanks a lot. Will try. When I tried to explore the core dump, I didn't get far. I had built with optimization, and several variables were not accessible. Will rebuild everything with -O0 today and re-run valgrind --smc-check=all. > Good luck ... Thanks. :-) m. _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
