0

I am trying to find out why a certain call to a TextBox takes unexpectedly long.

To do that, I open the EditCtls solution in VS2022 and attach it to VB6.

Then I perform the TextBox.Text = "Some very long value".

In VS2022, I can see that the following call takes very long:

return ::CallWindowProc(m_pfnSuperWindowProc, this->m_hWnd, uMsg, wParam, lParam);

Unfortunately, I can not investigate further what takes so long because the debugger steps over this line. I will not let me look furter into what is happening there under the hood.

The Autos window shows the following.

 comctl32.dll!0x6ef33530 (load symbols for additional information)

I am suspecting that I can step into the depths of what is happening if I load the symbols for "comctl32.dll".

To do that, I click "Tools" -> "Options" -> Debugging -> Symbols -> Load Only specific moduls -> "comctl32.dll".

Now, even with this done, it still steps over this line and does not let me investigate further what takes so long.

Did I make a mistake while trying to load the symbols for comctl32.dll?

Thank you!

enter image description here

Edit:

After re-opening VS2022, the warning / information is gone.

Now it shows the following, but it is still not stepping into the depths of the other dll. How could I do this?

Thank you!

enter image description here

tmighty
  • 10,734
  • 21
  • 104
  • 218
  • While a debug session is running, what does your Modules window say for this DLL? (Debug → Windows → Modules or CTRL + ALT + U) – Timothy G. Sep 14 '22 at 12:48

0 Answers0