[Octave-bug-tracker] [bug #44478] test __osmesa_print__.cc-tst crashes with Nvidia drivers

[Dan Sebald]

Follow-up Comment #101, bug #44478 (project octave):

I understand what you've done as far as linking.  However, as far as I
understand, OpenGL routines are slightly different.  All the glGetIntegerv(),
etc. are not directly callable functions from the application.  One has to
create a valid context and then the OpenGL routines are mapped somehow so they
can be called by the application.

I would think for OpenGL linking order shouldn't matter in theory (but of
course, that's currently the case).


  OSMesaContext ctx = OSMesaCreateContextExt (OSMESA_RGBA, 16, 0, 0, NULL);


should know the GL routines to map into the context.

Anyway, I have Mesa (with OSMesa) compiling, so I'm able to make modifications
to OSMesa, print out variables, etc. under the various scenarios.  If you have
something in mind I should try, let me know.

All I can add right now is a confirmation that the OSMesaCreateContext() seems
to go through the same program flow no matter the order of library linking. 
But, when it is -lGL -lOSMesa it's clear that the Mesa glGetIntegerv is not
being called.



    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?44478>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/