* Robert Osfield -- Monday 09 February 2009:
> I've just run valgrind and it generates a number of what it thinks are
> errors,
You are aware that I didn't use valgrind's standard tool "mecheck",
but its threading checker "helgrind"?
$ valgrind --tool=helgrind ./osgparticleeffects
^^^^^^^^
==31276== Thread #1: lock order "0x58F499C before 0x58F494C" violated
==31276== Thread #1: lock order "0x58F6A9C before 0x58F6AEC" violated
> OpenThreads and osgParticle have not changed in any substantial way
> for quite some while, so these errors have likely been there for a
> long time.
Sure, it may well be that the broken threading is old and has caused
segfaults before. :-P
> Do you get a crash in osgparticleeffects? If so how quickly?
None. But OSG is a library. Whether examples crash or not is IMHO
not really relevant, *if* there are bugs in the lib. Sure, we can
just assume/pretend that helgrind is buggy and osg is bugfree. ;-)
m.
_______________________________________________
osg-users mailing list
[email protected]
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
