I want to reopen this issue (now in a right subforum). I still have a problem with profiling golang application on windows 10 with manually generated .pdb files. Below steps worked for a few profile sessions and i dont know why (seems like something specific mustve happen), because after app rebuild (and .pdb regenerate) that never worked again:
I got it working. Firstly i built application with exported, uncompressed dwarf symbols:
go build -gcflags="all=-N -l -E" -ldflags="-compressdwarf=false" -o main.exe
Next step was to convert dwarf symbol to .pdb with cv2pdb tool as it was quite important that i run profiler on Windows.
It wasnt working even despite i specified folder where profiler should search for that .pdb file (the Add Symbol File Location(s) field). I copied .pdb file manually to the folder under Symbols Download Path field at it magically started to work.
CheatEngine didnt had problem to resolve debug symbols generated that way, so i think this problem may be specific to AMDuProf. Additionaly this: https://community.amd.com/t5/server-gurus-discussions/amd-uprof-does-not-see-my-pdb-file/m-p/42820 topic seems very related to mine. What else can you suggest to me to try?
