What's the best way to diagnose a GL crash?
I mean a specific "kind" - which typically happens at a render call such as glDrawArrays/glDrawElements... And only on "specific" hardware. Not all systems. Same code usually works just fine on modern nvidia/ati cards, but usually older intel laptops that support 2.1 have this problem - even though this is (as far as i know) 2.1-compliant code... And yet again, SOME older intel laptops also DO work, aswell as most modern ones.
I know the "usual" candidates: ...
Assure there are no GLerrors - there are none.
Use a GL debug context - usually the systems that crash like this actually also usually crash on simple context creation when specifying debug context.
Sometimes I hear "GLDebugger" - But, 1) I've never used that, and 2) am assuming you'd have to know specifically what to look for as i think it just provides general state information and probably wouldn't have anything specific/highlighted to a crash within the GL render function call ?
There have been things in the past that have also caused this that I've actually sorted out... For example, if you have a GL client state enabled and you don't send that attribute - it will crash on some (even modern, usually nvidia) cards. Even though ati card probably won't crash.
So it seems like it might be something similar to that. So for example - other than "knowing" that you should not -have a GL client state enabled when not sending that attribute- ... How would someone be able to successfully diagnose this issue?
Edited by 3TATUK2, 12 January 2014 - 03:55 AM.