[Mesa-dev] MESA and KOTOR

[Federico Dossena]

If I put printf("HELLO MESA\n"); into wglGetProcAddress it prints it, so 
some code from Mesa is certainly being executed.

The reason why I suspect that I have a windows dll loaded is that when 
it calls wglGetProcAddress("wglMakeContextCurrentARB") it seems to be 
inside a small DLL, while mesa is like 18mbytes. It doesn't look like 
mesa's dll at all to me... Is there any way I can tell for sure?


Il 2017-03-13 12:59, Emil Velikov ha scritto:
> [Adding back mesa-dev, since it seems like you've dropped it by accident]
>
> On 13 March 2017 at 11:42, Federico Dossena <dossenus91 at gmail.com> wrote:
>> Thanks for the reply.
>>
>> Ok, I have a few new findings:
>> - It seems that I was wrong, the function that it fails to get the address
>> of is actually wglMakeContextCurrentARB!
> Afacit Mesa (st/wgl) does not advertise WGL_ARB_make_current_read,
> hence why the function pointer is NULL.
>
> if the program does not check for the extension alongside the
> eglGetProcAddress, then it's broken and you'd need to either
> a) address that in the program
> b) or, add support for the extension in st/wgl
>
>> - Inside opengl32.dll I see it keeps getting the pointer and deleting it
>> until it finally returns 0
>> - The thing is... I don't know if that's Mesa or windows's opengl32.dll. I
>> am very sorry, I really suck at debugging low level code
>>
> Simple printf("HELLO MESA\n"); or similar will tell you exactly
> where/what you're using.
>
>> If someone here has some skill at using stuff like IDA pro, I will happily
>> send all the files so we can work together.
>>
> Since you've got the code for Mesa you really don't need any such
> tools. But if anyone's interested to help you out they know how to
> contact you.
> I won't be able to offer much more help, I'm afraid.
>
> -Emil