Preventing Debug Spam in eVC4

Question

I have an application that I need to debug on a target system.

All the relevant TRACE macros are in place to send messages to the debug window, however, I'm having difficulties in finding a way to prevent the spam there.

You see, this application is regularly creating & terminating threads, so I am getting a large amount of "The thread 0x23CF2B8A has exited with code 0 (0x0)" messages.

I've looked through the various menu options but I can't seem to find a way to disable this automated output.

Is there any way I can do this to clean up my debug window?

Answer 1

Sounds like you could do with a worker thread pool or a fixed number of threads.

Should you go with a fixed number of threads, you will also gain performance, i.e. when using as many threads as CPUs.

Another argument for not creating large amounts of threads on the fly is backward-compatibility. Windows used to leak resources (on XP SP1, if I remember correctly) when creating/destroying threads, so that the process eventually could not ::CreateThread(). (Hopefully this is fixed by now, but don't count on it.)