tracy
tracy copied to clipboard
wolfpld
Feature to Always be Listening?
My use case is I have relatively short lived processes, usually just pressing the "connect" button and then running it is enough. I don't really want to use the feature that prevents the program from exiting. But sometimes the same process runs multiple times and the one I need to profile isn't always the first one, or I need to profile them all. Not sure how this would work if there's multiple processes running at the same time. If that would be limited in some way. That does happen, generally it is just one process running one after the other.
It would be really useful to just have a "start listening" button and then it'll capture everything until "stop listening" is pressed or otherwise. Then having a list to choose from the traces with some details about them would be very useful.
You can decide which process should wait for incoming connection at exit by using TRACY_NO_EXIT environment variable, instead of compile-time define.
Multiple concurrently running processes will bind to other listening ports.
The issue is scripts and other tools use this process, so even just using an environment variable in that way will be troublesome.
Running multiple instances of Tracy causes the other instances to stop listening after the first process connects with one of the instances.