Cannot Debug the DLL??

[Guest]

Hi

I need help to debug the code in Dll I have myCom.dll and myCom.pdb files
but I canot debug myCom.dll.

Thanks

 

[Scott Allen]

Are you getting some sort of error message? I'm assuming you are
loading the dll into a process and trying to debug the process, not
just the dll. They don't stand on thier own.

 

[Guest]

I am using C#.net I build MyCom.dll in Debug mod , so I get 2 file in Debug
folder, one is MyCom.dll and MyCom.pdb.
when I add references that dll in project and break point in code when I
want go in dll then I get one message " There is no source Code Available for
the current location"
and that give one option to open Disassembly.
I think .pdb file help to debuging?

that help you to understand my question

 

[Scott Allen]

Yes - the PDB is a symbol file that helps the debugger find more
information about the executing code.

Make sure the PDB is copied into the main project directory, that is
/bin directory for asp.net, and that it is built in debug mode.

 

[Guest]

Yes I copy that file into bin directory but still I CANNOT debug the code I
am geting message box "there is no source Cide Availble for the current
location" so can you help me how I do debug.

Thanks

 

[John Peterson]

I have the same problem in a regular C++ project. Vistual Studio can't find the source code for one of the projects (a dll). The Modules window show no errors, it shows that the symbols are loaded for the right file and for the right location. I also know that the exe is actually using that exact file that is listed in Modules, so it's not the problem that I have multiple dll files. But VS still can't understand where the source code is. However, I can see the function names in the Disassembly (the functions are shown with blue text and are of the form "Class::Function:"), so I can kind of manually find my way to the corresponding source code. But VS is supposed to do that job for me, now debugging takes ten times longer. I tried enabling Options > Debugging > Native > Load DLL exports but that made no difference, and I don't see why it should since VS thinks it loaded the symbols (the pdb file). Can anyone understand how this problem occurs? I also tried cleaning the project (and double check that all files were removed), and the rebuild it, but that made no difference either. And I also actually have the source code, so it's not one odd function that is linked in from an external library that it naturally can't find the source code for, I can identify the lines the the Disassembly to the source that is right there in the project.

Best Regards
JP