K
Kevin960129
Guest
I am using mspdbcmf.exe (14.16.27030.1) to generate full pdbs from fast link pdbs built by Visual Studio 2017 15.9.11 build tools. That works and the symbols are uploaded to our symbol server successfully.
On a separate machine I attach to the running process and try to set breakpoints in the modules that I uploaded symbols for and I can't. I get the no executable code at location error. I can put a breakpoint on the line if I build the code locally. So I know there is code there.
If I break the program, I can see that VS downloaded symbols for the module and I can see call stack info. But, I get the "Source information is missing from the debug information for this module" message.
There is very little information on fast link and mspdbcmf.exe so I can't be sure I am doing something wrong. mspdbcmf.exe doesn't have many settings. I am simply doing mspdbcmf.exe /nologo /errorreport:none file.pdb.
I have also inspected the pdb and it looks like it has source files listed, tho I haven't determined how to check if it has source file line info.
Anyone know what I may have missed or if there is a bug that has been fixed?
Continue reading...
On a separate machine I attach to the running process and try to set breakpoints in the modules that I uploaded symbols for and I can't. I get the no executable code at location error. I can put a breakpoint on the line if I build the code locally. So I know there is code there.
If I break the program, I can see that VS downloaded symbols for the module and I can see call stack info. But, I get the "Source information is missing from the debug information for this module" message.
There is very little information on fast link and mspdbcmf.exe so I can't be sure I am doing something wrong. mspdbcmf.exe doesn't have many settings. I am simply doing mspdbcmf.exe /nologo /errorreport:none file.pdb.
I have also inspected the pdb and it looks like it has source files listed, tho I haven't determined how to check if it has source file line info.
Anyone know what I may have missed or if there is a bug that has been fixed?
Continue reading...