This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(297.6, 64%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EF%3C/text%3E%3C/svg%3E)
I am trying to debug a MFC app, and when I put a breakpoint inside of my code, I got:
the breakpoint will not currently be hit no symbols have been loaded for this document
Of course, I am aware to have pdb file just near by my exe, and I have checked/unchecked "Enable Just My Code", and other options, none of them had worked. Why ? What else should I check in order to have my breakpoints as functional ?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(92.8, 12%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDL%3C/text%3E%3C/svg%3E)
You don't need to have the EXE/PDB "near by" each other.
Ensure the EXE/DLL you're debugging is the one that you've built and that its built as a debug one with debugging information. If it doesn't match, or doesn't have debug information, then that's what happens.
Check the VS modules window pane when you're debugging too.
I have compiled right now the test project:
They are in the same folder, and they are new, and there is no other pdb files inside of my test project.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(214.4, 95%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBZ%3C/text%3E%3C/svg%3E)
First, I suggest that you could clean the project and rebuild the project. Delete all pdb files in the program directory.
If it doesn't work, you could select Debug -> Windows -> Modules. You'll see a list of all the assemblies that are loaded into the process. Locate the one you want to get debug info for. Right-click it and select Symbol Load Information. You'll get a dialog that lists all the directories where it looked for the .pdb file for the assembly. Verify that list against the actual .pdb location. Make sure it doesn't find an old one. In normal projects, the assembly and its .pdb file should always have been copied by the IDE into the same folder as your .exe, i.e. the bin\Debug folder of your project.
Besides, Make sure you are debugging in Debug mode and the project settings are x86 or x64.
I have deleted all generated files, because is a simple test project. Still the same behavior ...
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(294.40000000000003, 8%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EVL%3C/text%3E%3C/svg%3E)
For C# based solution, I had to select "IIS", right-click on it and close it, clean solution, and then try to restart debugging it again, it worked.
There are more ways here : Solving error "the breakpoint will not currently be hit" in Visual studio ( Multiple ways)
Hope it helps
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(268.8, 23%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESA%3C/text%3E%3C/svg%3E)
This kind of helped me
I have tried:
Why ?
Could you provide a minimal example or code snippet? This will help reproduce and solve the problem.
There is no point to attach a sample project, because this issue is acting on any test project, it's not a project issue, is a VS2017 issue ... I guess is a VS2017 settings, but I don't know which one.
I have tested a sample project on another PC, with a fresh installed VS2017, and this issue is not present.
So it must be a setting in your project. I'm sorry I don't know which switch in your VS 2017 project must be set. But you say you have a running project on another PC. You can copy your project to the other PC to check if it complains the same way.
But the easiest way to find the difference is to compare both project settings.
If you don't find anything, then maybe you should reinstall VS 2017.
Regards, Guido
I see that an error message "PDB Symbol reader could not be loaded " is present. According to this SO thread about VS2017 pdb-symbol-reader-could-not-be-loaded a repair or reinstall of VS2017 resolved the problem.