different options used on Vtune for analysis.

attempt to compile lame.exe with the debug version of libstdc++.

Makefile

@@ -17,8 +17,7 @@ OUTPUT_FOLDER = $(basename $@)
 #  $(foreach v, $(.VARIABLE), $(info $(v) = $($(v))))
 #  -gdwarf-2 for debug information for intel VTune Profiler.
 %.exe : %.cpp
-	g++ $< -g3 -gdwarf-4 -o $(basename $@)\$@
-
+	g++ $< -g3 -gdwarf-4 -o $(basename $@)\$@ 
 clean :
 #	del $(basename $(f))\$(f)
 	'$(ProgramFiles)/Git/usr/bin/rm.exe' -rf $(basename $(f))\$(f)

ToDo/ToDo.txt

@@ -18,8 +18,7 @@ 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 
-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 
+11JUN20
 results/analysis (still doesnt link source files however...)
-Have a release and a debug version of executables -> change Makefile
+Have a release and a debug version of executables -> change Makefile
+maybe go over Linux? maybe use Valgrind at a later date?

Vtune Profiling/README.txt

@@ -17,6 +17,15 @@ The profiler using "pulling" at a given interval, in this case it is about 1ms.
 analysis results. This is the main issue
 we had for VTune aside from the gcc arguments we found mentioned above.
 
-09JUNE20
+09JUN20
 ! 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.
+results/analysis (still doesnt link source files however...) this needs to be done everytime to see function names.
+
+11JUN20
+tried to use the below to compile with the supposed debug version of libstdc++ in the Makefile
+g++ $< -L C:\MinGW\lib\gcc\mingw32\8.2.0\debug\ -lstdc++ -D_GLIBCXX_DEBUG -g3 -gdwarf-4 -o $(basename $@)\$@
+This doesn't seem to work and also does not produce the debug symbols we want with VTune anyways.
+VTune is still acting randomly today - i.e. sometimes we get lame.cpp to reference main, sometimes not. Still stuck on libstdc++ debug symbols added.
+Today when opening up VTune, it forgot the prior instructions to start analysis (i.e. fold paths and what project executable to use).
+Program also crashed upon running for the "first run of the day". Analysis results "catch" maybe 1/5 times when using the "User-Mode Sampling" option for 
+analysis.