No symbols have been loaded and pdb file missing

the breakpoint will not currently be hit no symbols have been loaded for this document
a matching symbol file was not found in this folder
no symbols have been loaded for this document vscode
pdb not loaded visual studio
the breakpoint will not currently be hit no symbols have been loaded for this document vs 2019
no symbols have been loaded for this document c++
visual studio pdb files in release mode
the breakpoint will not currently be hit no symbols have been loaded for this document vs 2013

I'm trying to understand why I get the "The breakpoint will not currently be hit. No symbols have been loaded for this document" message, when try to debug my web site application (note: no web application, in case it matters)

So far I found out that the pdb (project debug database) file is as important as the source code, and it should appear in the bin folder, but for whatever reason the file is missing, just some dll's are placed there, actually there is no pdb file in the entire directory.

My first question is: There should be a pdb file regardless whatever the kind of project that is being developing. Correct?

Second question: How can I re-create that file again, or what steps needs to be done in order to debug the project again?

The breakpoint will not currently be hit. No symbols have been, The pdb files were being generated. I did however find that if I debug on the call to the class library, I could step into the library. "No Symbols have been loaded for this document" Go to the Modules window (Debug > Windows > Modules) and check whether your module is loaded. If your module is loaded, check the Symbol Status column to see whether symbols have been loaded. If symbols are not loaded, check the symbol status to diagnose the issue.

You have to have compilable code to get the pdb. It sounds like you do.

Usually what is happening is that you have setup your build to be "Release" instead of "Debug".

http://msdn.microsoft.com/en-us/library/wx0123s5.aspx

If you are creating a web application, your configuration files might also have a "Retail" setting. If set to true, you are always in "Release" mode, even if it says otherwise in your build configuration.

http://msdn.microsoft.com/en-us/library/ms228298(v=vs.80).aspx

Set symbol (.pdb) and source files in the debugger, The Visual Studio debugger uses .pdb files to determine two key pieces of information while debugging: By default, if you have built a DLL or an .exe file on your computer, the The symbol files for other modules are not loaded. Always shows the disassembly when source or symbol files are not found. No symbols have been loaded for this document" message with editorconfig file in project windows 10.0 visual studio 2017 version 15.3 debugger Sergio Eduardo Antonio reported Aug 20, 2017 at 02:23 AM

To generate .pdb files in Release, you need to set your project's properties:

Compile\Advanced Compile Options\Generate Debug Info => 'pdb-only' or 'Full'

Package/Publish Web\Exclude generated debug symbols => untick this

"The breakpoint will not currently be hit. No symbols have been , No symbols have been loaded for this document" message with editorconfig file in project "A matching symbols file was not found in this folder". .pdb file of the project have not copy in debug\Bin folder then it could not load symboles (. pdb� The debugger also searches for symbol files in the following locations: The location that is specified inside the DLL or the executable (.exe) file.By default, if you have built a DLL or an .exe file on your computer, the linker places the full path and filename of the associated .pdb file in the DLL or .exe file.

I just had this problem, and it turns out my web.config was set to debug=false. Make sure that compilation debug=true in your web.config

<compilation defaultLanguage="vb" debug="true" batch="false" targetFramework="4.0">
  <assemblies>
    <!-- add references to gac assemblies here-->
  </assemblies>
</compilation>

The breakpoint will not currently be hit. No symbols have been , No symbols have been loaded for this document - Xamarin Forms : Uwp I was getting error that system is missing VC=14.0 SDK , I installed it, now every time it shows loading symbols. Cannot find or open the PDB file. When debugging, without a symbol file you are unable to set breakpoints on a specific line of code. If symbols are not loaded you will see a hollow circle with a warning symbol while in debug mode, and if you hover the mouse over it a tooltip will tell you that the breakpoint will not be hit because no symbols have been loaded.

Solved: Breakpoint No symbols have been loaded., No symbols have been loaded for this document." I understand that this is usually a result of the .pdb file associated with the DLL being either missing or� No symbols have been loaded for this document" message, when try to debug my web site application (note: no web application, in case it matters) So far I found out that the pdb (project debug database) file is as important as the source code, and it should appear in the bin folder, but for whatever reason the file is missing, just some dll's

No symbols have been loaded and pdb file missing, No symbols have been loaded for this document � Grasshopper When I select HelloGrasshopper.pdb, I get: A matching symbol file was not found in this folder. I am trying to remotely debug wcf service on IIS 6. It has been working fine until yesterday. Now breakpoints are not being hit and warning message says "No symbols have been loaded for this document". I've solved this by restarting iis and app pool, but it worked just for a few days. Now I have the same problem.

PDB Files: What Every Developer Must Know, I'm trying to understand why I get the "The breakpoint will not currently be hit. No symbols have been loaded for this document" message, when try to debug my� And the only pdb file on the /debug folder is vc100.pdb, and there are no other pdb files anywhere in the project folders. In properties C/C++ > Debug Information Format, I have set Program Database (/Zi). And runtime library is set to Multi-threaded Debug (/MTd). Am I missing any other setting that's causing not to create the pdb files?

If you have any questions about PDB files ask a question in the comments, email me I've been to countless companies to help them debug those bugs costing When you load a module into the process address space, the debugger uses two Finally, if the debugger does not find the PDB file in the Symbol Server cache� No symbols have been loaded for this document." I understand that this is usually a result of the .pdb file associated with the DLL being either missing or out-of-date, but I have carefully ensured that the .pdb and .dll files are synchronized and both are in the folder from which the DLLs are being accessed.

Comments
  • Hi Tim, thanks for clarify, but I don't see the W3WP.EXE process running in the Task manager. And another question, now I can debug my website again like I said, but I still have some dlls that the symbols haven't loaded yet, Any ideas of how to fix this?
  • I assume you're running through the VS debugger instead of attaching to a process. Try deleting your temporary ASP.NET files and running the debugger again.
  • I can't delete the temporary asp.net files even if I close VS, I have to log off and then log on again, does it sound weird to you?
  • I've seen IIS lock the files on me too, not weird at all. (It drives me nuts at times) Try iisreset /stop, close any web browsers that are connected to the site, close VS, and try deleting the files again. After you're done remember to do an iisreset /start.
  • Thanks, hey you know what? in some pages the breakpoint works (appear filled) but in others don't, still the weird things :s
  • Updated answer with another potential solution.
  • the Release mode still generates pdb files
  • @AdrianIftode Sometimes, yes. Sometimes, no. stackoverflow.com/questions/291214/…
  • True, thanks. There is also the compilation section in the web.config file were compilation options can be set. It is for the generated dll(s) by ASP .Net for the aspx and ascx files. In case there are some <script runat="server"> sections
  • In the Web Site case the code behind files are compiled by ASP .Net not by you with Visual Studio, so there are no dll and pdb files in bin folder, these files are managed by ASP .Net when the site is "online". Bin folder can contain other dll and pdb files though.
  • Yep. Too bad every article on ASP.NET security says that this is a major security risk. Want no security and line numbers in your stack traces? Tough...
  • That only applies in a prod environment, and rightly so.
  • Maybe a bit out of place to discuss this in the comments, but why on earth is it right that you can't know the line numbers in your real-life, prod-environment unhandled exceptions?