minor fix to VTune - allows functions to be seen in analysis/results.

ToDo/ToDo.txt

@@ -18,6 +18,8 @@ Microsoft does not gurantee that a file will be written and be able to be read.
 the link below may have a possible solution. Since Msft writes files "randomly", when trying to read or modify the same file the program is unable
 to access the file. The below link will potentially help in detection of Msft's read write redirect (Msft claims that they do it both directions...). 
 https://stackoverflow.com/questions/14005081/how-to-detect-file-redirection-to-the-windows-virtualstore 
-07JUN20
+09JUN20
 Add the Microsoft API debug information into VTune Profiler - so other winAPI calls can be tracked, for instance Sleep. 
+! adding srv*C:\local_symbols_cache_location*http://msdl.microsoft.com/download/symbols when running analysis in VTune will add function names in the 
+results/analysis (still doesnt link source files however...)
 Have a release and a debug version of executables -> change Makefile

Vtune Profiling/README.txt

@@ -15,4 +15,8 @@ having the object or sources files in the working directory is not necessary.
 
 The profiler using "pulling" at a given interval, in this case it is about 1ms. If your program executes faster than the profiler, you won't see it in the 
 analysis results. This is the main issue
-we had for VTune aside from the gcc arguments we found mentioned above.
+we had for VTune aside from the gcc arguments we found mentioned above.
+
+09JUNE20
+! adding srv*C:\local_symbols_cache_location*http://msdl.microsoft.com/download/symbols when running analysis in VTune will add function names in the 
+results/analysis (still doesnt link source files however...) this needs to be done everytime to see function names.