Windbg pdb file not found

Unfortunately this didn't tell anything too specific so I captured a minidump from the phone and went straight to WinDBG for further analysis. Now my issue is that although I can load the crashdump into WinDBG, I'm unable to get the appropriate symbol files as WinDBG is constantly complaining about not finding the required files.

I've changed the required sympaths as necessary so I've been trying to use the official MS online repositories but WinDBG just doesn't want to cooperate and get the files. Unfortunately I couldn't find an offline symbols repository for Windows Phone 10 and therefore I'm stuck with the analysis. The symbols would be required in order to nail down the root cause making the F crashes. So far I can only see that this is possibly a driver related issue but with the symbols I would be able to get a better answer on what's going on exactly.

For those who are interested I provided some details about this Lumia XL problem in another thread found here page 35 :. Microsoft R Windows Debugger Version All rights reserved. In this command you need to provide the full name of the binary name along with the extension. Otherwise you might see the message like below.

Please provide the full image name, including the extension i. If none of the symbol files match with the binary file then. When you get this do the following. Enable verbose mode for symbols loading by running the command! And run the. Check for the error messages it prints. As you can see none of the symbol search paths have the Myapplication.

Another thing you can notice in the above error is that, Windbg looks for the symbols files in a sub directory with the name myapplication. This is because we used the keyword SRV in the symbol search path which indicates that this path need to be used as a symbol server path. For symbol servers, to identify the files path easily, Windbg uses the format binaryname.

Now back to the symbol loading issue for Myapplication. As the existing paths does not have this file, we need to add the path where the file is present. Then we can add this path to the symbols search using. In our example, we need to run. Now we are into another problem. Windbg detected the symbol file but it says that the symbol file is not matching with the exe file.

If you see this issue, you need to crosscheck with your build numbers and pick up the right pdb file. As you can see it looks for a matching pdb in all the search paths.

As it does not find any, it loads the mismatched pdb in the end. I hope this post has helped you in understanding how symbols loading works in Windbg. Wednesday, March 11, AM. Here omitting first indirection for better clarity curl needs quotation marks : curl -vL -o baz.

Tuesday, March 17, PM. Hello, since the system dlls are not yours, and as long as you don't want to debug system dlls, the messages are ok and you can ignore the messages.

Regards, Guido. Wednesday, March 11, PM. Hi, Thank you for posting here. Thursday, March 12, AM. Thanks for your information!

Thursday, March 12, PM. Is this a network problem? Can't tell from your output. Sometimes pdbs may be missing on the MS symbol server - e. In general a retransmit of a pdb you already have in your symbol cache, may give a hint about connectivity to the symbol server. In case of missing symbol files you may probably want to send an email to windbgfb at microsoft dot com but they need 'PDB7 Sig' and 'Age' cache path for identification.

With kind regards. Friday, March 13, AM. Thanks a lot! For symchk just recall, that connection may fail, when it loads the dbghelp. Should load the one where symchk. But for VisualStudio no idea at the moment, should be fine. Friday, March 13, PM. HTTP request sent, awaiting response Unable to establish SSL connection.

Sunday, March 15, AM. On my side wget --version GNU Wget 1.