Exploding WGL Code

[Baker]

Code: Select all

void GetWGLExtensions (void)
{
   const char *(*wglGetExtensionsStringARB) (HDC hdc);
   const char *(*wglGetExtensionsStringEXT) ();

   if (wglGetExtensionsStringARB = (void *) wglGetProcAddress ("wglGetExtensionsStringARB"))
      wgl_extensions = wglGetExtensionsStringARB (maindc);
   else if (wglGetExtensionsStringEXT = (void *) wglGetProcAddress ("wglGetExtensionsStringEXT"))
      wgl_extensions = wglGetExtensionsStringEXT ();
   else
      wgl_extensions = "";
}

Only explodes with certain compile optimizations. Inconveniently, debug compile optimizations aren't one of the exploding ones, making locating exactly what was crashing somewhat of a pain. Those wgl extensions aren't really that useful for Quake (the only one I ever was interested in for Quake was the 2ndary way to detect swap control that some stupid Intel Display Adapters use, but there is a GL_swap_hint something or rather in the regular GL extensions for those, it is named in a non-standard way, yeah, but it is in the stock GL extensions list).

I ran into this messing around with my current project.

[Spike]

prototype with undefined argument list!! EEK!
no idea what would be crashing in that code though.
if in doubt, printf/OutputDebugStringA are your friends, when it crashes only with non-debug builds anyway.
make sure you're not editing the string somehow? :s

[Baker]

It doesn't edit the string any where.

But I was a bit surprised that different optimizations would cause it crash or not crash. A slightly unfun mystery. I ended up inserted about 40 "MessageBox" pop-ups and when it stopped at #17, I had it located but surprised to see that it was this.

Oh well, I found the crash point and it didn't take so long.

[mh]

GLEW - because life's too short to load GL extensions by hand.

[revelator]

As mh says easiest way to get around all this