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(51.2, 31%, 14%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDW%3C/text%3E%3C/svg%3E)
I'm using MFC as a shared DLL in a program with an EXE and a number of my own DLLs, some of which use MFC.
Using VS-2019, when I step through my program's DEBUG build, it won't step into the MFC library source code.
How do I get it to do so?
Dave
![](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)
Do you have the "just my code" debugging option set?
In addition to unchecking "Just My Code" you will also need to setup up the debugger to load the symbol files for the MFC Dlls. specify-symbol-dot-pdb-and-source-files-in-the-visual-studio-debugger
Thank you,
I've checked that justMyCode is unset in both the VS Debug/Options menu and in each of the project properties.
And following your link I now seem to be downloading the .pdb's from Microsoft. (I need to try and use the versions on my computer so I can work off line, but we're OK for now.) Thanks.
Dave
![](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(9.6, 11%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDZ%3C/text%3E%3C/svg%3E)
Hi @David Webber ,
As RLWA32's answer, you could specify the symbol file location in debugging options, and vs will load it for your mfc DLL.
By the way, if this answer is helpful you, you could click "Accept Answer". This can be beneficial to other community members.
Best Regards,
Dylan
You can use the MFC symbol files that were installed with Visual Studio. In the debugging options uncheck the Microsoft Symbol Server and add the path to the symbol files that were installed with Visual Studio.
For example, in a VS2017 installation (32 bit VM) the locally installed MFC symbol files are used as follows -
Of course you would specify the appropriate path on your own system to use the local files.