Abstraction around emit zone callstack callbacks.

[sunnlok]

Hey there, i have some questions regarding instrumentation through an abstraction around the emit callbacks. Due to our architecture supporting more than one profiler backend, we are abstracting away the actual instrumentation calls behind our own macros and static data. For tracy, this means that it lives in its own dynamic library and gets the begin zone/end zone calls via what basically ammounts to a function pointer call. The source location data is provided for the actual callsite and placement allocated for tracy into our static profiling data. Obviously for callstack sampling this now provides an issue, since tracy now thinks that all zones begin inside the callback. My question now is if its possible to tell tracy to ignore X number of functions on the callstack before the ___tracy_emit_zone_begin_callstack call. It seems that tracy already has a mechanism internally to include its own functions from this.

And the other problem, which is probably related to this, is tracy not showing sampling percentages on the source view.