apitrace VS ProcDump-for-Linux

You have several tools, this can be done by printing debug messages using extensions such as KHR_debug, or using specific tools which will inject themselves between your OpenGL calls and your driver such as apitrace or RenderDoc. I recommend running your program in RenderDoc regularly even if everything seems to work fine as it may help you catch some subtle bugs.

That said, the profiling situation for non-NV users is not completely hopeless. You can still use API timer queries to get an idea of how long events take on the device. Tracy also supports GPU profiling, but I suspect it's just a fancy way of inserting timer queries. apitrace also claims to support profiling OpenGL apps, but I'd be wary of overhead as it's doing a lot of other things besides profiling.

At first I thought Feral probably used it accidentally, but this thread about the symbol's use in apitrace seems to shed some light:

I don't see anything wrong with your code, altough I'm not familiar with Avalonia or Silk. I suggest you try to use apitrace for (a probably long and painful day) debugging it.

I get that it's hard to debug without direct access, but isn't there some dump or log that they could generate and provide? Maybe something like using apitrace?

Pierre-Eric Pelloux-Prayer @pepp · 6 months ago Developer https://github.com/apitrace/apitrace/blob/master/docs/USAGE.markdown is the basic doc. For Steam games I usually go to the game's folder (probably $HOME/.steam/steam/steamapps/common/Indivisible) and try to run the game with apitrace (apitrace trace indivisible-executable). It should print a line to indicate where the trace file is written to (apitrace: tracing to somefile.trace.

Now I'll preface this by saying that I never bothered with makefiles but hardcoding which compiler to use doesn't seem like a good idea to me. Apparently the internet also agrees.