Breaking news, Windows libc runtime emits diagnostic events only useful to someone who has the debug symbols for the program?

I don't really see a big problem here?...

Visual C++ telemetry functions for EWT -> Windows 10 -> Microsoft -> Conspirational theories!

Meanwhile BigG is reading your emails.....

Naming it "telemetry" was probably the biggest mistake in here. That said, why was this feature set up to be opt-out instead of opt-in, if it can't be used without the symbols anyway? I get the use of opt-out on features that have security implications, checked iterators and the like. But this? I don't need the compiler silently adding spurious code regardless of what the additional code does. MS has a particularly bad habit of doing this stuff in the compiler, I don't think clang will tend to do this sort of thing at all.

MS has a particularly bad habit of doing this stuff in the compiler, I don't think clang will tend to do this sort of thing at all.

Yea, clang's callstack is crystal clear:

int main(int argc, char **argv)
int  __libc_start_main()
void __static_init_thunk()
void __init_heap()
void __allocate_stack()
void __start_thread()
void __record_six_months_of_iPhone_geolocations()