We’ve moved

You may have noticed that the previous post on this blog is from several years ago.  This doesn’t mean the Visual Studio debugger team has stopped blogging about the work we’re doing on your behalf, but we moved our blogging to the Diagnostics channel on the Visual Studio ALM blog. Additionally for a great overview…


Visual Studio debugger fails to catch unhandled exception for a Windows Form or WPF Application?

Ever begin debugging a Windows Form to have the form close suddenly without the debugger alerting you to the exception?  Or have you ever been stepping through the Form_Load event handler (or a method called by the Form_Load event handler) in a WPF application only to have it unexpectedly bring up the form instead of…


Can’t hit breakpoints in a plug-in or can’t debug .NET 2.0/3.0/3.5 from a mixed mode .exe project with Visual Studio 2010?

With Visual Studio 2010 came the release of Visual Studio .NET 4.0.  .NET 4.0 adds a lot of great features and new capabilities; however with .NET 4.0 came a new 4.0 debug engine in Visual Studio 2010 (so there are now two managed debug engines, 2.0/3.0/3.5 and 4.0).  Ordinarily if you are developing/debugging your managed…


Why don’t I see “Debug with Mixed” when debugging the dump of a managed process in Visual Studio 2010

It has been well publicized that Visual Studio 2010 introduced the ability to debug dumps of managed processes in mixed mode (as opposed to the old days of native debugging + SOS in the Immediate Window).  The one fact about this new feature that often gets overlooked or forgotten is that mixed mode debugging only…


Jinx: Visual Studio plug-in for debugging multi-threaded code

Today I’m going to introduce a plug-in for Visual Studio (still in beta) that helps to speed up finding concurrency bugs in multi-threaded applications. Example of a concurrency bug Consider an application that has two threads (“Thread A” and “Thread B”) that share a common stack. Each thread reads (pops) one value off the stack…


Help! My console windows won’t go away

Many of you may be seeing an issue where your console windows won’t close after you stop debugging.  The symptoms of this issue include: ·         The console application does not terminate as expected after you stop debugging ·         The console windows can be moved, minimized and maximized, but cannot be closed ·         The corresponding process…

114

Introducing IntelliTrace

In the upcoming release of Visual Studio 2010 we’re going to be rolling out a very cool new feature called IntelliTrace to enhance and expand the Visual Studio debugger experience. In a nutshell, IntelliTrace is a black box for your debugging experience. As your programs run IntelliTrace can be running as well, collecting lots of…

0

Visual Studio 2010 Beta2 hang while debugging?

Causes We have received numerous reports of Visual Studio 2010 Beta2 hanging while debugging. The two most common causes identified for this were a bug in IntelliTrace and an Internet Explorer 8 bug when debugging web applications. IntelliTrace Hang You can determine if your hang is caused by the IntelliTrace issue by disabling IntelliTrace. To…


What is a dump, and how do I create one?

What is a dump and how is it useful? A dump is a snapshot of an application at the point in time the dump is taken. It shows what was executing, what modules are loaded, and if saved with heap contains a snapshot of what was in the application’s memory at that point in time…


Remote debugging on Win7 error: Unable to start debugging …

If you are running msvsmon on a Win7 machine and are seeing the following error message when attempting to remote debug: —————————Microsoft Visual Studio—————————Error while trying to run project: Unable to start debugging.This operation returned because the timeout period expired.—————————OK   The issue is that the firewall is not setup properly on the Win7 machine for…

0