I'm trying to set up WinDbg to be able to debug one of my applications sitting out on a server that's a pain in the ass to get access to. I'm trying to set it up as a process server (using dbgsrv), and I've gotten to the point where I can connect to the machine without problems and actually start the application on demand using the process server. Once there though, that's where the snag is.
When everything loads, all the symbols load for Windows (through Microsoft's symbol server), but the executable image doesn't. It comes up in the module list as:
||0:0:000> lm
start end module name
00400000 0051e000 image00400000 C (no symbols)
Despite the fact that I have my symbol and source paths set correctly on my local machine. I've tried just about everything I can think of, but I can't figure it out. I can't trace through code or set breakpoints, but I'm so damn close. Everything works fine locally, and if I run locally on the server.
Anyone?
When everything loads, all the symbols load for Windows (through Microsoft's symbol server), but the executable image doesn't. It comes up in the module list as:
||0:0:000> lm
start end module name
00400000 0051e000 image00400000 C (no symbols)
Despite the fact that I have my symbol and source paths set correctly on my local machine. I've tried just about everything I can think of, but I can't figure it out. I can't trace through code or set breakpoints, but I'm so damn close. Everything works fine locally, and if I run locally on the server.
Anyone?
Facebook
Twitter