Part of the Khronos Group

The Industry's Foundation for High Performance Graphics

from games to virtual reality, mobile phones to supercomputers

Page 2 of 2 FirstFirst 12
Results 11 to 12 of 12

Thread: glDeleteTextures() throws "An invalid HANDLE was specified"-exception C0000008

  1. #11
    Senior Member OpenGL Pro
    Join Date
    Jan 2007
    What we're actually interested in is comparing the call stack before the exception occurs with the call stack after the exception occurs. That will tell you if execution jumped to somewhere it shouldn't have.

  2. #12
    Junior Member Regular Contributor
    Join Date
    Nov 2012
    Oldenburg, Germany
    That would really be a hard issue. Sadly I cannot reproduce the exception anymore. But my thought would be that if the stack got messed up the program flow would not be normal afterwards. The cleanup-routine has some local variables which would have been messed up then resulting in an access Violation. The this pointer of the objects always looked normal at the time of exception. No bad vftable, no member-variables containing rubbish, normal program execution after the exception. If I remember right the exception was thrown in another thread of nvogl. Not in the main thread of the program.
    I cannot help myself but assume the impossible: My program generates that same exception in a totally unrelated-to-OpenGL context when messing around with the console and stderr (that's an issue for itself) in a more-or-less controlled manner. The nvogl surely would not contain any references to those standard streams, wouldn't it?
    Last edited by hlewin; 08-05-2014 at 04:28 AM.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts