Remember me

Lost Password?

Register now!


Who's Online
47 user(s) are online (30 user(s) are browsing Forums)

Members: 0
Guests: 47


Support us!


Report message:*

Re: Porting apitrace

Subject: Re: Porting apitrace
by Capehill on 2019/4/6 12:29:48


Yeah, before edit, there was a copy-paste bug where I tried to patch the wrong interface and that crashed. Those patch_ functions should be probably generated by a macro to avoid such silly issues.

I guess shaders are given numbers (glCreateShader) from 256 upwards, so that's why those numbers appear in glCompileShader input, too. Daniel knows.

Executable might be detected by FindTask() somehow ("who is calling this function") but I don't think it's super important at this phase.

So at least we can do now some basic debugging when needed.

Powered by XOOPS 2.0 © 2001-2016 The XOOPS Project