V Studio 2003 Doesn't Load Supporting DLL Debug Symbols for Windows Service Remote Debug

V Studio 2003 Doesn't Load Supporting DLL Debug Symbols for Windows Service Remote Debug

Post by INGSO » Wed, 09 Feb 2005 18:19:45



Using remote debugging, I can attach to a windows service and run it in
debug mode in VS.Net 2003.

The problem is this service uses two supporting dlls. On the remote
service, the dlls have been registered in the GAC. They are also in the
service's directory, along with their associated *.dbg symbols. Yet, any
breakpoint in the dlls is not hit.

The dlls are part of the project file, and breakpoints in them can be hit
when I debug locally.

Is there additional configuration that I need to perform when I debug a
windows service with supporting dlls remotely?

Should the *.dbg files be in some other location?

--
Texeme
http://www.yqcomputer.com/
 
 
 

1. V Studio 2003 Doesn't Load Supporting DLL Debug Symbols for Windows Service Remote Debug

2. Remote Debugging ASP.net 2.0 Web Service (no symbols loaded?)

I'm trying to remotely debug an asp web service, published to my
IIS6.0 server, using VS.net 2005

So far, I've published the website, installed remote debugging
monitor, connected to the debugging monitor from VS on my host
machine, and attached to the w3wp.exe process. However breakpoints
that I set in my webservice code in VS are flagged as "the breakpoint
will not currently be hit. no symbols have been loaded for this
document".

I have hunted around on the server, and found a .pdb file for
"App_Web_wbscx-fh.dll" (C:\WINDOWS\Microsoft.NET\Framework
\v2.0.50727\Temporary ASP.NET Files\mercury\1e74d20e\72afe63b
\App_Web_wbscx-fh.pdb), where mercury is the name of my deployed app.

However my web service code is located in App_Code, and there are no
symbols loaded for App_Code.dll, and I can't find a pdb file for this
dll on the server. I've found a couple on my local machine, but when I
try and manually load these symbol files in under Debug->Windows-
Modules, I get an error saying that the files don't match the modules.

Does anyone have any ideas? Should I really need to be messing around
with pdb files? I would have thought that should all be automated when
I start debugging.

3. Install Debug DLL's for remote debugging

4. Mixed mode debugging - run debug load/unload imagehlp.dll

5. Remote Debugging and loading symbols

6. remote debugging no symbols loaded asp.net

7. Remote Debugging - No symbols loaded

8. Visual Studio 2003 Debugging on Windows server 2003 64bit question

9. Trying to remotely debug (Windows Server 2003) with Visual Studio .NET 2003 and get this error:

10. Way to not load executables symbols when debugging a DLL?

11. Visual Studio 2003 Debugging on Windows server 2003 64bit question

12. remotely debug (Windows Server 2003) with Visual Studio .NET 2003 and get this error

13. Remote debugging in Visual Studio .Net 2003 Trial

14. Visual Studio 2003 remote debugging

15. Visual Studio 2003 Debugging on Windows server 2003 64bit question