Hello: > > You might want to try and get a stack trace with gdb. If it turns out > that you have vector iterators or OpenThreads in the stack trace, then > it's probably a question of calling setText() while another thread is > running the draw traversal. >
:). Wish I could. The setText is completly hosing everything. I have tried the gdb on the executable. I usually have to reboot. > To be safe with all threading models that OSG supports, setText on an > osgText object must be called in the update traversal. I've run into > this lately myself, and the tricky part is that it won't necessarily > crash each time you call setText(), it depends on timing issues. > > Using an update callback fixed it for me. I just have a setText() I only update a text object within the update traversal of the scene graph. Thank you for the suggestion though. I am also suspect about the version of freetype being compiled in. I am downloading the latest and greatest release form freetype.org and will try that instead of the system freetype. Take care Garrett _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
