Jan Rysavy

I tried to load the PDB using the current version of C:\Program Files\Microsoft Visual Studio\2022\Community\DIA SDK (14.36.32532.0) and the method loadDataFromPdb returns the error E_PDB_FORMAT. The same test with older msdia140.dll (14.29.30035.0) works.

VTune 2023.1.0 works fine also with C:\Program Files\AMD\AMDuProf\bin\msdia140.dll (version 14.29.30035.0).

This also probably explains why Profiler in Visual Studio (2022) stopped displaying function names in recent versions. It uses newer versions of msdia140.dll.

I can confirm replacing C:\Program Files (x86)\Intel\oneAPI\vtune\2023.1.0\bin64\amplxe_msdia140.dll (version 14.34.31942.0) with version 14.28.29910.0 from VTune 2022.4.1 solves this problem!

Created issue: https://bitbucket.org/anders_melander/map2pdb/issues/5/intel-vtune-20231-does-not-load-generated

I just want to add that I installed an older version of VTune 2022.4.1 and the function names are displayed correctly. The problem seems to be related to the new version VTune 2023.1.

Are any of you running MAP2PDB with the current version of Intel VTune 2023.1? Both AMD uProf and WinDBG correctly load my PDBs created by the latest version of MAP2PDB, but VTune only shows function addresses without symbolic names.

I would like to implement support for reading of JEDI .jdbg files: https://bitbucket.org/anders_melander/map2pdb/issues/2/parser-for-jdbg-files Does anyone know if .jdbg parser code exists? Otherwise I can probably write it based on TJclBinDebugGenerator.Create: https://github.com/andremussche/asmprofiler/blob/b785168f7caec8ff91d59d912dfb0e9e4519f803/Source/EXT/jcl/JclDebug.pas#L2358 Edit: nevermind, found .jdbg parser - TJclBinDebugScanner.