I can't debug an MFC app anymore
-
I recently un-installed and re-installed Visual Studio 6.0. Something I noticed at the end of the installation process (I don't remember seeing this before) was a message box that popped up saying"
Setup has installed an icon in the Microsoft Visual C++ 6.0 group, that will allow you to install a subset of the Windows NT system symbols(.DBG) files....
For easier application debugging, it is strongly recommended that you install these files..When I try clicking on the icon they mentioned, I get messages saying that the files I am trying to install don't coincide with the DLLs in my system32 area. This is strange because it is asking me to load the CD that I just used to install Visual Studio. Anyways, I built a small dialog app with only one button. When I try to debug this app even with no breakpoints, after the dialog box for the app is put on the screen, I get a message box that says
User breakpoint called from code at 0xa725cd..
and the break pointer is at that address in machine code. If I put a breakpoint inside OnInitDialog(), everything works fine, the code stops and I can look at watch points. But, once the app is allowed to run to where the dialog box is displayed, I get what I mentioned above. Once I "stop debugging" the output window has the following in it
Loaded 'ntdll.dll', no matching symbolic information found.
Loaded 'C:\WINDOWS\system32\kernel32.dll', no matching symbolic information found.
Loaded symbols for 'C:\WINDOWS\system32\MFC42D.DLL'
Loaded symbols for 'C:\WINDOWS\system32\MSVCRTD.DLL'
Loaded 'C:\WINDOWS\system32\gdi32.dll', no matching symbolic information found.
Loaded 'C:\WINDOWS\system32\user32.dll', no matching symbolic information found.
Loaded symbols for 'C:\WINDOWS\system32\MFCO42D.DLL'
Loaded 'C:\WINDOWS\system32\comctl32.dll', no matching symbolic information found.
Loaded 'C:\WINDOWS\system32\advapi32.dll', no matching symbolic information found.
Loaded 'C:\WINDOWS\system32\rpcrt4.dll', no matching symbolic information found.
Loaded 'C:\WINDOWS\system32\uxtheme.dll', no matching symbolic information found.
Loaded 'C:\WINDOWS\system32\msvcrt.dll', no matching symbolic information found.
Loaded 'C:\WINDOWS\system32\dllt.dll', no matching symbolic information found.
First-chance exception in MoreButtons.exe (DLLT.DLL): 0xC0000005: Access Violation.
The program 'D:\PROJECTS\MoreButtons\Debug\MoreButtons.exe' has exited with code 0 (0x0).Is it possible that I might have some corrupt files in my system32 folder????
-
I recently un-installed and re-installed Visual Studio 6.0. Something I noticed at the end of the installation process (I don't remember seeing this before) was a message box that popped up saying"
Setup has installed an icon in the Microsoft Visual C++ 6.0 group, that will allow you to install a subset of the Windows NT system symbols(.DBG) files....
For easier application debugging, it is strongly recommended that you install these files..When I try clicking on the icon they mentioned, I get messages saying that the files I am trying to install don't coincide with the DLLs in my system32 area. This is strange because it is asking me to load the CD that I just used to install Visual Studio. Anyways, I built a small dialog app with only one button. When I try to debug this app even with no breakpoints, after the dialog box for the app is put on the screen, I get a message box that says
User breakpoint called from code at 0xa725cd..
and the break pointer is at that address in machine code. If I put a breakpoint inside OnInitDialog(), everything works fine, the code stops and I can look at watch points. But, once the app is allowed to run to where the dialog box is displayed, I get what I mentioned above. Once I "stop debugging" the output window has the following in it
Loaded 'ntdll.dll', no matching symbolic information found.
Loaded 'C:\WINDOWS\system32\kernel32.dll', no matching symbolic information found.
Loaded symbols for 'C:\WINDOWS\system32\MFC42D.DLL'
Loaded symbols for 'C:\WINDOWS\system32\MSVCRTD.DLL'
Loaded 'C:\WINDOWS\system32\gdi32.dll', no matching symbolic information found.
Loaded 'C:\WINDOWS\system32\user32.dll', no matching symbolic information found.
Loaded symbols for 'C:\WINDOWS\system32\MFCO42D.DLL'
Loaded 'C:\WINDOWS\system32\comctl32.dll', no matching symbolic information found.
Loaded 'C:\WINDOWS\system32\advapi32.dll', no matching symbolic information found.
Loaded 'C:\WINDOWS\system32\rpcrt4.dll', no matching symbolic information found.
Loaded 'C:\WINDOWS\system32\uxtheme.dll', no matching symbolic information found.
Loaded 'C:\WINDOWS\system32\msvcrt.dll', no matching symbolic information found.
Loaded 'C:\WINDOWS\system32\dllt.dll', no matching symbolic information found.
First-chance exception in MoreButtons.exe (DLLT.DLL): 0xC0000005: Access Violation.
The program 'D:\PROJECTS\MoreButtons\Debug\MoreButtons.exe' has exited with code 0 (0x0).Is it possible that I might have some corrupt files in my system32 folder????
-
I recently un-installed and re-installed Visual Studio 6.0. Something I noticed at the end of the installation process (I don't remember seeing this before) was a message box that popped up saying"
Setup has installed an icon in the Microsoft Visual C++ 6.0 group, that will allow you to install a subset of the Windows NT system symbols(.DBG) files....
For easier application debugging, it is strongly recommended that you install these files..When I try clicking on the icon they mentioned, I get messages saying that the files I am trying to install don't coincide with the DLLs in my system32 area. This is strange because it is asking me to load the CD that I just used to install Visual Studio. Anyways, I built a small dialog app with only one button. When I try to debug this app even with no breakpoints, after the dialog box for the app is put on the screen, I get a message box that says
User breakpoint called from code at 0xa725cd..
and the break pointer is at that address in machine code. If I put a breakpoint inside OnInitDialog(), everything works fine, the code stops and I can look at watch points. But, once the app is allowed to run to where the dialog box is displayed, I get what I mentioned above. Once I "stop debugging" the output window has the following in it
Loaded 'ntdll.dll', no matching symbolic information found.
Loaded 'C:\WINDOWS\system32\kernel32.dll', no matching symbolic information found.
Loaded symbols for 'C:\WINDOWS\system32\MFC42D.DLL'
Loaded symbols for 'C:\WINDOWS\system32\MSVCRTD.DLL'
Loaded 'C:\WINDOWS\system32\gdi32.dll', no matching symbolic information found.
Loaded 'C:\WINDOWS\system32\user32.dll', no matching symbolic information found.
Loaded symbols for 'C:\WINDOWS\system32\MFCO42D.DLL'
Loaded 'C:\WINDOWS\system32\comctl32.dll', no matching symbolic information found.
Loaded 'C:\WINDOWS\system32\advapi32.dll', no matching symbolic information found.
Loaded 'C:\WINDOWS\system32\rpcrt4.dll', no matching symbolic information found.
Loaded 'C:\WINDOWS\system32\uxtheme.dll', no matching symbolic information found.
Loaded 'C:\WINDOWS\system32\msvcrt.dll', no matching symbolic information found.
Loaded 'C:\WINDOWS\system32\dllt.dll', no matching symbolic information found.
First-chance exception in MoreButtons.exe (DLLT.DLL): 0xC0000005: Access Violation.
The program 'D:\PROJECTS\MoreButtons\Debug\MoreButtons.exe' has exited with code 0 (0x0).Is it possible that I might have some corrupt files in my system32 folder????
That message box is talking about the NT4 debug symbols (remember, VC6 is from 1998). Not having symbols for the system DLLs won't affect your ability to debug, the only thing you'll be missing is in the call stack - you won't see meaningful function names for parts of the stack that are in system DLLs. The real problem is that "dllt.dll" is malware according to a Google search.
--Mike-- Visual C++ MVP :cool: LINKS~! Ericahist | PimpFish | CP SearchBar v3.0 | C++ Forum FAQ
-
That message box is talking about the NT4 debug symbols (remember, VC6 is from 1998). Not having symbols for the system DLLs won't affect your ability to debug, the only thing you'll be missing is in the call stack - you won't see meaningful function names for parts of the stack that are in system DLLs. The real problem is that "dllt.dll" is malware according to a Google search.
--Mike-- Visual C++ MVP :cool: LINKS~! Ericahist | PimpFish | CP SearchBar v3.0 | C++ Forum FAQ
-
Cool Mike.... Thanks a lot... What should be my next step... Merely delete "dllt.dll" or run Adaware? I know that is a rhetorical question but I wante to know if "that's all there is to it"... Again... Thank you very much Pierre
You can try deleting the file, but chances are it will be in use and it won't be that easy to delete it. Using AdAware or a similar scanner is the way to go.
--Mike-- Visual C++ MVP :cool: LINKS~! Ericahist | PimpFish | CP SearchBar v3.0 | C++ Forum FAQ