Reply – Re: Mesa 17.2.0 renderer driver name change error, causes GLProfile not mapp...
Your Name
Subject
Message
or Cancel
In Reply To
Re: Mesa 17.2.0 renderer driver name change error, causes GLProfile not mapped initialization error
— by ccaudle ccaudle
gouessej wrote
My fix should work as "OpenGL version string" contains "Mesa ":
Yes, so is there a way to make sure the fix is working as intended, and to have jogl dump out which code path it took to determine the profile to use?

Where does that error message of profile not mapped come from?
$ grep "profileImpl GL4bc" *.java
$ pwd
~/rpmbuild/BUILD/jogl-v2.3.2/src/jogl/classes/jogamp/opengl

I went up to the src directory and grepped for "profileImpl GL4bc" in all the .java files and all the .c files but did not find it.  Is there a file of message strings separate from the code that I did not see?

This is the file which was compiled, the patch is correct, yes?

    final boolean isWindows = Platform.getOSType() == Platform.OSType.WINDOWS;
    final boolean isDriverMesa = glRenderer.contains(MesaSP) || glRenderer.contains("Gallium ") || glVersion.contains(MesaSP);
    final boolean isDriverATICatalyst;
    final boolean isDriverNVIDIAGeForce;

After looking through the file quickly it seems error strings are built up by concatenating shorter strings along with variables or defined strings, so probably why a simple grep cannot find that error message.

What are next debug steps to determine why the "GL3bc -> profileImpl GL4bc !!! not mapped" error is still occuring?