wolfpld
RFC: an annotation to report errors internal to Tracy
I think we should consider adding an instrumentation directive for Tracy itself, to report internal errors that get "silently ignored". One such example are the various ETW trace API calls, that simply return on error, without any warning to the user.
This internal logging mechanism should be available for the server too (as it would also double as a debug utility).
We could just make them show up as a regular TracyMessage in the Message panel, with a proper prefix (e.g., [Tracy:Client:<Component>:<Severity>], [Tracy:Server:<Component>:<Severity>]), with maybe a checkbox to filter them in/out, or have a dedicated Message panel for them.
Curious to know what others think.
@GabrielSiliceum has been working on this recently.
I also would like to have logs (mostly what TRACY_VERBOSE prints to stdout) to be sent to the server too so that we can debug why system profiling fails.
It may be best to have a proper internal logging api that will, among other things, also print to stdout/stderr. It's also nice to have a central point to put breakpoints and such.
Redirecting/piping stdout and stderr while also forwarding/duplicating the stream to the original endpoints, is tricky due to eternal/environment issues that it's hard for Tracy to control.