Ian Romanick wrote:
Here's the deal. glXGetProcAddress *NEVER* returns NULL. It returns
a pointer to a dispatch function. If you request an unknown function,
it will dynamically generate a dispatch for it. Try calling
'glXGetProcAddressARB((const GLubyte*)glThisFunctionDoesntExist);.
--- Stephane Marchesin [EMAIL PROTECTED] wrote:
Ian Romanick wrote:
Here's the deal. glXGetProcAddress *NEVER* returns NULL. It returns
a pointer to a dispatch function. If you request an unknown function,
it will dynamically generate a dispatch for it. Try calling
Jon Smirl wrote:
--- Ian Romanick [EMAIL PROTECTED] wrote:
Here's the deal. glXGetProcAddress *NEVER* returns NULL. It returns a
pointer to a dispatch function. If you request an unknown function, it
will dynamically generate a dispatch for it. Try calling
'glXGetProcAddressARB((const
--- Keith Whitwell [EMAIL PROTECTED] wrote:
Why do you dynamically generate a dispatch for unknown functions instead of
just
returning null? What does this dispatch dispatch to?
The linux OpenGL ABI requires that GetProcAddressARB return the same value in
all contexts, including ones
Jon Smirl wrote:
--- Ian Romanick [EMAIL PROTECTED] wrote:
Here's the deal. glXGetProcAddress *NEVER* returns NULL. It returns a
pointer to a dispatch function. If you request an unknown function, it
will dynamically generate a dispatch for it. Try calling
'glXGetProcAddressARB((const
Allen Akin wrote:
On Thu, May 27, 2004 at 05:55:29PM -0700, Jon Smirl wrote:
| ... What does this dispatch dispatch to?
In most implementations, a dynamically-generated stub that jumps through
a known offset in a vector of function pointers. That entry in the
vector might not
I'm using Redhat xorg-x11-6.7.0-2
The addresses coming back from these get_proc_address calls don't look quit
right. When one is used in context-gl.get_program_iv_arb() it segfaults. I'm
using an R128 which does not have hardware shaders.
Should these calls be returning values as if they were
Jon Smirl wrote:
I'm using Redhat xorg-x11-6.7.0-2
The addresses coming back from these get_proc_address calls don't look quit
right. When one is used in context-gl.get_program_iv_arb() it segfaults. I'm
using an R128 which does not have hardware shaders.
Should these calls be returning values as
Stephane Marchesin wrote:
Jon Smirl wrote:
I'm using Redhat xorg-x11-6.7.0-2
The addresses coming back from these get_proc_address calls don't look
quit
right. When one is used in context-gl.get_program_iv_arb() it
segfaults. I'm
using an R128 which does not have hardware shaders.
Should these
On Thu, May 27, 2004 at 05:55:29PM -0700, Jon Smirl wrote:
| Why do you dynamically generate a dispatch for unknown functions instead of
| just returning null? ...
Since I'm one of the people who proposed that behavior, I guess I should
save Ian the trouble of explaining. :-)
There are several
10 matches
Mail list logo