Marcos Slomp

(we'd also need to modify some APIs related to symbol resolution to look externally to another process, but that's doable)

Thanks! Yeah, `fork()` would not work on Windows anyway. I'll see if I can make a proof-of-concept that piggy-backs on (and extends) the existing `TracyClient.cpp` code. The idea would be...

> inject Tracy as a .dll into the process directly. Yeah, this could work. DLL injection is becoming more difficult on recent Windows versions, but since it needs to run...

(I'll get around to fixing it, just registering it here until I can switch context and work on a D3D12 app to repro/fix)

> Should we break the API&ABI to add this to the current TracyMessage* defines? No, `TracyMessage(msg)` as is should just become the "common denominator", e.g. `TracyLog(User, Info, msg)`, as you...

> No, but I suppose we could? Nah, I think we're good as is. Should people bring this matter in the future, we can always implement it later. ~On a...

In my opinion, we should introduce just one new "overarching" macro to the public API: ``` #define TracyLogString(level, string, length, color, callstack_depth) ... ``` and leave further macroing and abstractions...

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...

An embeddable, visual debugging tool for [Halide](http://halide-lang.org): https://github.com/halide/visual_debugger 

I can verify that this worked. However, the Pipeline serialization feature does not seem to consider this new target feature. (Moving this discussion over to https://github.com/halide/Halide/issues/8802)