March 2004 - Posts
On several occasions I have seen a feature request to debug an exe without a project. I love this feature request because we already have it. Just open the exe as a project. You can even configure the project to attach to the exe instead of launch it
Read More...
On another blog, I saw a feature request to be able to script start debugging so that the debugger could launch/attach to multiple projects. There isn't automation support for launch, but there is something that is easier to use - a solution can be configured
Read More...
One of the debates that has gone on in the debugger team is who should be responsible for launching the remote debugging components. VC has traditionally required that the user launch msvcmon.exe. VJ automatically launched debugging components. In VS
Read More...
It’s not widely advertised, but you can set up a file share pretty easily that has everything you need for remote native debugging. This article has the list: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vsdebug/html/vctskInstallingRemoteDebugMonitor.asp
Read More...
One of the problems with remote debugging is the lack of consistency with symbol loading. For managed debugging, we load symbols on the debuggee machine. For native debugging, we load symbols on the debugger machine. This means that if you are, for example,
Read More...
Sometimes processes vanish without putting up the unhandled exception dialog first. Here are a few of the reasons why this can happen. Bad exception handling. Exception handling code is a bit tricky, and if you get it wrong, the OS may not get the chance
Read More...
For those of you who haven’t had the joys of the Win64 registry, I decided that I would blog about it. When Win64 came around, clearly the Windows team had to think about how to support having 32-bit and 64-bit applications installed side-by-side.
Read More...
