Robert Osfield wrote: > Hi Alessandro, > > On 7/25/07, alessandro terenzi <[EMAIL PROTECTED]> wrote: > >> I tried again to go deeper with the debugger and I managed to gather the >> information shown in the screen shot... I can say also that when I hit 's' >> the second time, the debugger goes through the instructions displayed in the >> screen shot for 3 times, then the green, blue, yellow and red writings are >> displayed in the application and stepping over the highlighted instruction >> causes the access violation. I think I cannot provide further details with >> the tools/knowledge I have so far. >> > > Alas its still not deep enough. My best guess as to the cause is > either a flaky OpenGL drivers handling of the GPU stats extensions, or > a problem with keeping the graphics context current for some reason. > > A call to other Windows users, could you please test out osgviewer and > stats on your machine and report back if it works fine or not. > This is not directly relevant to the problem at hand here, but has anybody ever tried building OSG with _GLIBCXX_DEBUG defined? It's a hardly documented feature gnu's libstdc++, but seems to enable extra runtime checks on iterators and such being valid.
Paul _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
