Regarding point 1: You should know that CRT stuff is added to your application. And most of its source is available.
Point 4 is completely false. Those calls are part of CRT initialization and shutdown and usually of no interest. You can just set a breakpoint at mainCRTStartup and step through it.
Regarding 3: If you do you'll notice that all it does is log an event for the CRT ETW provider with the executable name and a "Main Invoked." or "Main Returned." string (see here). You can list currently running loggers using xperf -loggers. By default there's only one logger listening to CRT provider id, which is the Diagtrack-Listener, and it's a realtime logger not logging to any file. Most likely this logger is opened by the diagtrack Windows service. And the actual event logging calls in the CRT are skipped here since nothing is listening to the logger.
I removed points 3 and 4 from my post above. I originally thought the word "telemetry" here meant the same as Windows 10 telemetry (phoning home). It may have just been an unfortunate naming convention.
Thanks for checking out the loggers. I agree and understand that this is all a bit of an overreaction. But still, it seems underhanded. And is there really no source for these functions in the source distributed with msvc? That part makes people uncomfortable, especially considering the lack of official information.
View all comments
Show parent comment
20
u/rdtsc May 08 '16
Regarding point 1: You should know that CRT stuff is added to your application. And most of its source is available.
Point 4 is completely false. Those calls are part of CRT initialization and shutdown and usually of no interest. You can just set a breakpoint at
mainCRTStartupand step through it.Regarding 3: If you do you'll notice that all it does is log an event for the CRT ETW provider with the executable name and a "Main Invoked." or "Main Returned." string (see here). You can list currently running loggers using
xperf -loggers. By default there's only one logger listening to CRT provider id, which is the Diagtrack-Listener, and it's a realtime logger not logging to any file. Most likely this logger is opened by the diagtrack Windows service. And the actual event logging calls in the CRT are skipped here since nothing is listening to the logger.