Cannot step into MFC source at debugging time - VS2017

Question

Cannot step into MFC source at debugging time - VS2017

C V 46

Hi all,

As in the subject I cannot simply step into the MFC source code at debugging time.
My dev environment is fully updated. I'm using VS2017 professional.

Steps:
I created a default MFC project, compiled it and run it step by step but when I want to step into MFC code it says it cannot find the code. And even if I browse and point VS under
C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\VC\Tools\MSVC\14.16.27023\atlmfc\src
I attached a screenshot about the message it says.

The properties of the projects are all left default and the platform toolset is: Visual Studio 2017 (v141)

The symbols are correctly downloaded.

Any idea how to fix that?

Thanks!
264656-bug.png

RLWA32 49,536 Reputation points

2022-11-28T09:08:04.787+00:00

Using VS2017 Community version 15.9.51 I could not reproduce the issue. I used the new MFC Application template to create an MFC MDI project and accepted the defaults (including using MFC as a shared DLL). A breakpoint was set and then the VS Debugger stepped into the MFC source code without displaying any messages. The debugger option "Enable Just My Code" was unchecked.
C V 46 Reputation points

2022-11-28T21:14:02.177+00:00

Thanks for the reply.

The debugger option "Enable Just My Code" was unchecked.

Mine too. It is unchecked.

If I create a default console application I can step into the c++ library source without issues.

I feel there is a sort of misalignment as far as I can understand. But I don't know where.
RLWA32 49,536 Reputation points

2022-11-29T09:30:01.257+00:00

Just guessing here -- maybe the files in the symbol cache are outdated. You could try emptying the cache so that the VS2017 debugger downloads fresh copies.
C V 46 Reputation points

2022-11-29T10:18:08.143+00:00

Just guessing here

No problem.

maybe the files in the symbol cache are outdated. You could try emptying the cache so that the VS2017 debugger downloads fresh copies.

Already done.

It seems that the MFC lib (shared dll), linked to my project, is misaligned or a different version with the MFC sources deployed under the VS2017 installation...
RLWA32 49,536 Reputation points

2022-11-29T10:20:32.72+00:00

Have you let the debugger use the out-of-sync source files to see what happens?
C V 46 Reputation points

2022-11-29T10:45:32.943+00:00

Yes and it steps on blank source codes line or comments, a clear evidence of misaligning.
Under
C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\VC\Tools\MSVC
there are two folders 14.11.25503 and 14.16.27023.
I tested the debugger against the source in both folders and in both cases is misaligned.
RLWA32 49,536 Reputation points

2022-11-29T11:08:51.437+00:00

Under C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\VC\Tools\MSVC there are two folders 14.11.25503 and 14.16.27023.

Thats odd. My fully updated VS2017 Community version only has the 14.16.27023 folder. The MFC source files in the atlmfc\src\mfc subfolder are all dated 6/13/2020 2:48 PM.
C V 46 Reputation points

2022-11-29T17:30:36.533+00:00

That folder with that version depends on which components you installed.

The MFC source files in the atlmfc\src\mfc subfolder are all dated 6/13/2020 2:48 PM.

Mine is 11/21/2018 21:08.
RLWA32 49,536 Reputation points

2022-11-29T17:32:56.237+00:00

Have you considered repairing/reinstalling VS2017? Or upgrading to VS2019/VS2022?
C V 46 Reputation points

2022-11-29T18:50:45.353+00:00

:)

I uninstalled the mfc library for VS2017 and installed them again but the issue is still there.

Of VS2019 and 2022 I have only the community version and doesn't let me create a desktop app with mfc, the checkbox is grayed out. Of VS2017 I have the professional one.

Before uninstalling VS2017 and installing it again I would prefer to submit a bug to Microsoft Feedback or alike to see if I got attention.

What do you suggest?

Thanks
RLWA32 49,536 Reputation points

2022-11-29T19:13:50.597+00:00

Of VS2019 and 2022 I have only the community version and doesn't let me create a desktop app with mfc, the checkbox is grayed out.

Perhaps you forgot to install the MFC support in VS2022/VS2019. For example, in the VS2022 Community Visual Studio Installer -
C V 46 Reputation points

2022-11-29T20:31:03.687+00:00

Please have a look:
RLWA32 49,536 Reputation points

2022-11-29T22:26:56.877+00:00

In my Community versions of VS2019 and VS2022 the only installed versions of MFC are for the latest versions.

You don't use the Windows Desktop Wizard to create an MFC Application or an MFC DLL. In the New Project wizard there are separate choices for these.

MFC Applicaiton -

MFC DLL -
C V 46 Reputation points

2022-11-30T07:43:36.91+00:00

You're right.

I tested both VS2019 and VS2022 with a MFC App. Only VS2022 doesn't suffer of the problem. That is I can step into the source code without problems.
Additionally I cannot browse the project resources inside the resource view, afxres.h is missing says VS2019. :)

At this point I would repair both VS2017 and VS2019 and see if that fix the problems.

I will let you know.

Thanks
C V 46 Reputation points

2022-12-01T09:31:50.6+00:00

After many troubles I reinstalled 2017, 2019 and 2022.

Short version: under VS2022 I can step into mfc code without problems, while under 2017 and 2019 not.

Under 2017 (it's the same for 2019) when I try to step into the mfc source code a dialog appears (bug0.png).
If I click on the first option or the second a new dialog appears (bug1.png) showing the misalignment of the linked library
and the mfc source I have on my pc (this time I have only the 14.16.27023 installed.
If at that point I click on Cancel on that dialog then a new window will appear with a some sort of log (bug2.png).

Of VS2017 I had the professional one since I had a msdn subscription. Of VS2019 and VS2022 I installed the community version.

Any idea?

Thanks
RLWA32 49,536 Reputation points

2022-12-01T10:40:03.627+00:00

At this point I suggest reporting your issues with VS2017 & VS2019 debuggers through VS. See how-to-report-a-problem-with-visual-studio
C V 46 Reputation points

2022-12-01T11:06:57.157+00:00

Thanks for your support.

The last strawberry:

I tried to add an accelerator as a resource and then I clicked on the first line to add the combination of keys...the entire VS2017 crashed! Unbelievable.
RLWA32 49,536 Reputation points

2022-12-01T11:21:35.82+00:00

You're welcome.

1 answer

Your answer

RLWA32 49,536 Reputation points

2022-11-28T09:08:04.787+00:00

Using VS2017 Community version 15.9.51 I could not reproduce the issue. I used the new MFC Application template to create an MFC MDI project and accepted the defaults (including using MFC as a shared DLL). A breakpoint was set and then the VS Debugger stepped into the MFC source code without displaying any messages. The debugger option "Enable Just My Code" was unchecked.
C V 46 Reputation points

2022-11-28T21:14:02.177+00:00

Thanks for the reply.

The debugger option "Enable Just My Code" was unchecked.

Mine too. It is unchecked.

If I create a default console application I can step into the c++ library source without issues.

I feel there is a sort of misalignment as far as I can understand. But I don't know where.
RLWA32 49,536 Reputation points

2022-11-29T09:30:01.257+00:00

Just guessing here -- maybe the files in the symbol cache are outdated. You could try emptying the cache so that the VS2017 debugger downloads fresh copies.
C V 46 Reputation points

2022-11-29T10:18:08.143+00:00

Just guessing here

No problem.

maybe the files in the symbol cache are outdated. You could try emptying the cache so that the VS2017 debugger downloads fresh copies.

Already done.

It seems that the MFC lib (shared dll), linked to my project, is misaligned or a different version with the MFC sources deployed under the VS2017 installation...
RLWA32 49,536 Reputation points

2022-11-29T10:20:32.72+00:00

Have you let the debugger use the out-of-sync source files to see what happens?
C V 46 Reputation points

2022-11-29T10:45:32.943+00:00

Yes and it steps on blank source codes line or comments, a clear evidence of misaligning.
Under
C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\VC\Tools\MSVC
there are two folders 14.11.25503 and 14.16.27023.
I tested the debugger against the source in both folders and in both cases is misaligned.
RLWA32 49,536 Reputation points

2022-11-29T11:08:51.437+00:00

Under C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\VC\Tools\MSVC there are two folders 14.11.25503 and 14.16.27023.

Thats odd. My fully updated VS2017 Community version only has the 14.16.27023 folder. The MFC source files in the atlmfc\src\mfc subfolder are all dated 6/13/2020 2:48 PM.
C V 46 Reputation points

2022-11-29T17:30:36.533+00:00

That folder with that version depends on which components you installed.

The MFC source files in the atlmfc\src\mfc subfolder are all dated 6/13/2020 2:48 PM.

Mine is 11/21/2018 21:08.
RLWA32 49,536 Reputation points

2022-11-29T17:32:56.237+00:00

Have you considered repairing/reinstalling VS2017? Or upgrading to VS2019/VS2022?
C V 46 Reputation points

2022-11-29T18:50:45.353+00:00

:)

I uninstalled the mfc library for VS2017 and installed them again but the issue is still there.

Of VS2019 and 2022 I have only the community version and doesn't let me create a desktop app with mfc, the checkbox is grayed out. Of VS2017 I have the professional one.

Before uninstalling VS2017 and installing it again I would prefer to submit a bug to Microsoft Feedback or alike to see if I got attention.

What do you suggest?

Thanks
RLWA32 49,536 Reputation points

2022-11-29T19:13:50.597+00:00

Of VS2019 and 2022 I have only the community version and doesn't let me create a desktop app with mfc, the checkbox is grayed out.

Perhaps you forgot to install the MFC support in VS2022/VS2019. For example, in the VS2022 Community Visual Studio Installer -
C V 46 Reputation points

2022-11-29T20:31:03.687+00:00

Please have a look:
RLWA32 49,536 Reputation points

2022-11-29T22:26:56.877+00:00

In my Community versions of VS2019 and VS2022 the only installed versions of MFC are for the latest versions.

You don't use the Windows Desktop Wizard to create an MFC Application or an MFC DLL. In the New Project wizard there are separate choices for these.

MFC Applicaiton -

MFC DLL -
C V 46 Reputation points

2022-11-30T07:43:36.91+00:00

You're right.

I tested both VS2019 and VS2022 with a MFC App. Only VS2022 doesn't suffer of the problem. That is I can step into the source code without problems.
Additionally I cannot browse the project resources inside the resource view, afxres.h is missing says VS2019. :)

At this point I would repair both VS2017 and VS2019 and see if that fix the problems.

I will let you know.

Thanks
C V 46 Reputation points

2022-12-01T09:31:50.6+00:00

After many troubles I reinstalled 2017, 2019 and 2022.

Short version: under VS2022 I can step into mfc code without problems, while under 2017 and 2019 not.

Under 2017 (it's the same for 2019) when I try to step into the mfc source code a dialog appears (bug0.png).
If I click on the first option or the second a new dialog appears (bug1.png) showing the misalignment of the linked library
and the mfc source I have on my pc (this time I have only the 14.16.27023 installed.
If at that point I click on Cancel on that dialog then a new window will appear with a some sort of log (bug2.png).

Of VS2017 I had the professional one since I had a msdn subscription. Of VS2019 and VS2022 I installed the community version.

Any idea?

Thanks
RLWA32 49,536 Reputation points

2022-12-01T10:40:03.627+00:00

At this point I suggest reporting your issues with VS2017 & VS2019 debuggers through VS. See how-to-report-a-problem-with-visual-studio
C V 46 Reputation points

2022-12-01T11:06:57.157+00:00

Thanks for your support.

The last strawberry:

I tried to add an accelerator as a resource and then I clicked on the first line to add the combination of keys...the entire VS2017 crashed! Unbelievable.
RLWA32 49,536 Reputation points

2022-12-01T11:21:35.82+00:00

You're welcome.

Answer 1

C V 46

Update:

If I build my program linking the MFC as static library then it works perfectly. Unfortunately I don't want to link MFC statically against my project.

Share via

Cannot step into MFC source at debugging time - VS2017

1 answer

Your answer