https://bugs.freedesktop.org/show_bug.cgi?id=95215
--- Comment #4 from Jamey Sharp <ja...@minilop.net> ---
(In reply to Ilia Mirkin from comment #3)
> (In reply to Jamey Sharp from comment #2)
> > (In reply to Ilia Mirkin from comment #1)
> > > Sounds like the game is buggy and needs fixing - I presume it runs fine on
> > > Catalyst drivers, which also don't support the ext.
> >
> > Hmm. Is apitrace mis-leading us here?
>
> More likely the game is buggy. Note that glXGetProcAddress("bla") != null.
> See https://dri.freedesktop.org/wiki/glXGetProcAddressNeverReturnsNULL/
OK, but __glewNamedStringARB *is* null when run on Mesa, so I guess GLEW's
semantics are different from glXGetProcAddress.
Sure, there is a game bug here: GLEW's documentation says that the game should
check if GLEW_ARB_shading_language_include is true, and doesn't say you can
check for a non-null function pointer instead.
That doesn't change the fact that tracing apparently changes the game's
behavior, which is obnoxious and leads to mis-diagnosed bug reports. Unless
you're saying that tracing is actually not changing the game's behavior?
--
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug._______________________________________________
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev
