Profiling after exit()

Stefan Koch via Digitalmars-d-learn digitalmars-d-learn at puremagic.com
Thu Jul 27 07:52:18 PDT 2017


On Thursday, 27 July 2017 at 14:30:33 UTC, Eugene Wissner wrote:
> I have a multi-threaded application, whose threads normally run 
> forever. But I need to profile this program, so I compile the 
> code with -profile, send a SIGTERM and call exit(0) from my 
> signal handler to exit the program. The problem is that I get 
> the profiling information only from the main thread, but not 
> from the other ones.
>
> [...]

You will need to run it single threaded.
If you want to use the builtin-profiler.


More information about the Digitalmars-d-learn mailing list