I suddently can't debug (in debug mode) on a VB.NET project developed on Visual Studio 2013 Community.
VS says first it can't load the symbols. I load them using the symbol servers and then it says I can't debug. The message says "No source available" (although it's definitely my code).
In the project's property I have activated the debug mode with full info and debug and trace active.
"Enable Just My Code" is disabled.
EDIT:
Microsoft.VisualStudio.Debugger.Runtime.dll doesn't load the symbols
When I go to the Modules' window and select "load symbols", VS loads it from the cache.
It can't find the symbols for the Debugger anywhere else.
C:\Desenvolvimento\Focagem\Gestinf\Código\Working Copy\TestWorkApp\bin\x86\Release\Microsoft.VisualStudio.Debugger.Runtime.pdb: Cannot find or open the PDB file.
C:\Windows\assembly\GAC_MSIL\Microsoft.VisualStudio.Debugger.Runtime\12.0.0.0__b03f5f7f11d50a3a\Microsoft.VisualStudio.Debugger.Runtime.pdb: Cannot find or open the PDB file.
f:\binaries\Intermediate\debugger\runtime.csproj__624416745\objr\x86\Microsoft.VisualStudio.Debugger.Runtime.pdb: Cannot find or open the PDB file.
C:\Windows\Microsoft.VisualStudio.Debugger.Runtime.pdb: Cannot find or open the PDB file.
C:\Windows\symbols\dll\Microsoft.VisualStudio.Debugger.Runtime.pdb: Cannot find or open the PDB file.
C:\Windows\dll\Microsoft.VisualStudio.Debugger.Runtime.pdb: Cannot find or open the PDB file.
C:\Users\joao.santos\AppData\Local\Temp\SymbolCache\Microsoft.VisualStudio.Debugger.Runtime.pdb\bbffb22f8979464b8744c7c973fbe2c01\Microsoft.VisualStudio.Debugger.Runtime.pdb: Symbols loaded.
Related
I am using VS 2022 (17.3.3) to debug a binary that has the symbols loaded. I would like to load up the disassembly, but the option Decompile Source To Symbol File is disabled. Does anyone know why it is not available/
Recently I compiled dotent runtime source 6.0.1 and aspnetcore source 6.0.1, and used Rider to debug aspnetcore project. Basically all dlls can be debugged with breakpoints, only Microsoft.Extensions.* cannot. Rider Debug Console outputs something like : "Loaded Assembly '/usr/local/share/dotnet/shared/Microsoft.AspNetCore.App/6.0.1/Microsoft.Extensions.Hosting.Abstractions.dll'
Loading module /usr/local/share/dotnet/shared/Microsoft.AspNetCore.App/6.0.1/Microsoft.Extensions.Hosting.Abstractions.dll in application domain 1:clrhost
Pdb file for assembly /usr/local/share/dotnet/shared/Microsoft.AspNetCore.App/6.0.1/Microsoft.Extensions.Hosting.Abstractions.dll was not found or failed to read ” , about 25 Microsoft.Extensions The .* pdb files are not getting after compiling the source code. How to get these pdb files? And how to set up to debug Microsoft.Extensions.*.dll? Not using SourceLink etc.
Given the following:
the 32-bit DLL code file of some old Firefox plugin (i.e. a DLL containing among other a Typelib, XSD and XSL entries), without source code or debug info, originally coded in C++ and compiled with Visual Studio,
the name and parameters of an exported function/method in this DLL (a function of the Firefox plugin, accessable in JS code),
Visual Studio Community 2013 running on Windows 7,
experience in C++ development, but not with COM or Firefox,
experience with debugging Intel assembler code,
a code license which does not prohibit disassembling the DLL,
I would like to do this: Load the DLL into some C++ code, and step on CPU level into the code of the function to find out what it exactly does.
Can you give me any hint on where to start and how get this done? I guess the DLL may need some Firefox-specific initialization before I can call the function which I would like to debug. Could this be done with the Firefox SDK, without source code and debug info for the DLL? Or may I succeed in "nakedly" loading the DLL, finding the entry point of the - rather simple - function (how?) and calling it?
Thanks for any hints.
If no pdb file or source code, it is hard for you to debug the dll file, since the debugger loads debugging information from the PDB file and uses it to locate symbols or relate current execution state of a program source code. Visual Studio uses PDB files as its primary file format for debugging information during debugging. If no those files, you couldn't debug that library.
Update:
We are dynamically loading a dll to one project using LoadLibrary() function, but if you want to step into your dll file, it really require the pdb file. A simple sample is that you could create and place one pdb file in the same folder as one simple custom dll library project located. I think Visual Studio will automatically search the directory and load them, you could find the information in your Debug modules windows.
The following case is not the same issue as yours, but it also shared us that it would load the pdb file if the dll file was really called by one project/process:
Does winbase::LoadLibrary() load .pdbs?
I've got a minidump from Windows Phone crash report. It contains a managed exception. I can open the minidump in VS2013, but when trying to debug as managed, I get the following:
Unable to managed debug this minidump. The matching version of
System.Runtime.dll could not be found on the Microsoft symbol server
or on the symbol search path. Make sure the computer has internet
access so the dll can be downloaded from Microsoft.
Additionally, in Output window, there's the following:
SYMSRV: e:\symbols\System.Runtime.dll\536B47F4a000\System.Runtime.dll not found
SYMSRV: http://msdl.microsoft.com/download/symbols/System.Runtime.dll/536B47F4a000/System.Runtime.dll not found
http://msdl.microsoft.com/download/symbols: Symbols not found on symbol server.
I have Microsoft Symbol Server enabled. There's a copy of System.Runtime.dll under C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\WindowsPhone\v8.1
Any ideas, please? Is there an alternative symbol server with WP8 symbols? I've tried excluding System.Runtime.dll from the list of modules to load symbols for; doesn't help.
EDIT: The bug report is here. If you're suffering from the same, please go there and place a "I can [reproduce] too".
I have a simple Test project where a CodedUITestMethod is created. The test method simply clicks the Windows Start button in the taskbar. The method is generated by the Coded UI Test Builder tool from Visual Studio 2010 Ultimate.
Then, I go to project's Properties page, Code Contracts tab.
Check the Perform Runtime Contract Checking check box.
Change the value of Contract Reference Assembly combo box to "Build".
Now I hit F6 to build the project and receive the 2 errors:
Reading assembly 'Microsoft.VisualStudio.TestTools.UITesting' resulted in errors.
C:\Program Files (x86)\Microsoft\Contracts\MsBuild\v4.0\Microsoft.CodeContracts.targets (240,5): error MSB3073: The command ""C:\Program Files (x86)\Microsoft\Contracts\Bin\ ccrewrite" "#CodedUITest_Contract2ccrewrite.rsp"" exited with code -1.
I have uploaded my project zip file to my codeplex project
Could someone download the project and see if they can reproduce the compile error? Thanks.
The problem is solved. It appears that Microsoft.VisualStudio.TestTools.UITesting.dll references another dll that is not added into the project.
Add Microsoft.VisualStudio.TestTools.UITest.Playback.dll in the folder C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\PrivateAssemblies\ solves the issue.
Thanks to David K Allen who answered the question on the msdn forum.