On May 11, 2005, at 10:02 AM, Christopher Niederauer wrote:
We are aware of an issue in the version of OpenGL Profiler that
shipped with Tiger where you will sometimes "catch" false thread
conflict errors around CGL calls when you use the "Break on thread
conflict" feature. If you are only using one thread to talk to your
carbon based OpenGL application, this "error" is likely something
you can ignore.
Glad to hear it is a know issue. I am also seeing the exact same
weird breaks as the OP in a single threaded carbon app.
This saves me from trying to figure out what is going on (which was
on my list since I tried GL Profiler on Tiger with our latest port).
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Mac-opengl mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/mac-opengl/email@hidden