Welcome to MSDN Blogs Sign in | Join | Help

Browse by Tags

All Tags » Tips and Tricks » Debugging   (RSS)

Quick Tip: Debugging Smart Device Unit Tests

While browsing MSDN today, I came upon a handy article that I wanted to share.   Titled 'How to: Debug while Running a Smart Device Unit Test ', it provides step by step instructions on debugging your test projects. There is one additional step

Command Line Debugging Revisited - Part 5: The X Command

In the previous installment, I talked about attaching to running processes using MDbg . As part of that discussion, I used the X command. Today, I'd like to spend a little time on X . The X command is one of those great features of MDbg that I think is
Posted by DavidKlineMS | 2 Comments

Using the .NET Compact Framework Remote Performance Monitor to Configure Diagnostic Options

Diagnostic, performance and debugging tools are very cool. The more tools available, the easier it tends to be to find and fix application issues. With Visual Studio 2005, several handy tools were added. I use the Remote Registry Editor and Remote File

The Error Log: A New Diagnostic in .NET Compact Framework v2 Service Pack 1

The recent release of Service Pack 1 for the .NET Compact Framework version 2 has added some very useful diagnostic tools. You may have already read about the .NET Compact Framework Remote Performance Monitor , and have hopefully used it to analyze the

Command Line Debugging Revisited - Part 1: Getting started with MDbg and .NET Compact Framework Version 2 Service Pack 1

It's been a while since I last wrote about using the command line debugger (cordbg) with the .NET Compact Framework. Quite a bit has changed in the world of .NET Compact Framework command line debugging since that time. With the release, last year, of

The Importance of Debugger Symbols: or Reloading Symbols while Debugging

Have you ever attached to a managed application and been greeted with the following message ... No symbols are loaded for any call stack frame. The source code cannot be displayed. ... and found that breakpoints could not be set, or that single step attempts

Using the Interop Log to Diagnose P/Invoke Call Issues

Sometimes, determining why an unmanaged function call (P/Invoke) has failed can be challenging. Fortunately, version 2 of the .NET Compact Framework has a new diagnostic log for this data -- the Interop Log. In June 2005, Steven Pratschner wrote a great

Diagnosing MissingMethodExceptions and TypeLoadExceptions using the Loader Log

Have you ever encountered a MissingMethodException or TypeLoadException when starting a .NET Compact Framework application? If you are running version 2 of the .NET Compact Framework, the Loader Log can help identify the source of the exception. For detailed

Debugging Multi-Threaded Applications III - Thread Specific Breakpoints

As mentioned in my first post in this series, debugging multi-threaded applications can be challenging. This installment talks about how to determine which of your application's threads are calling potentially threading sensitive methods. Using Visual

Debugging Multi-Threaded Applications II - Setting A Thread's Name Using The Debugger

Naming your application's threads can make debugging multi-threaded applications quite a bit simpler, especially if you have more than a couple of threads. Thread names can be set in code as shown below: // set the current thread's name Thread.CurrentThread.Name

Debugging Multi-Threaded Applications I - Deadlocks

Multi-threaded code can be challenging to write and debug. Today, I'd like to spend some time talking about one of the most common issues when writing multi-threaded code... deadlocks. Example deadlock To begin, let's examine an example of the "classic"
Posted by DavidKlineMS | 1 Comments

Resetting the source code associations in the Visual Studio debugger

Have you ever been debugging and found yourself looking at the wrong source code? Typically, this happens to me when I just hit the escape key at the dialog prompting me for the source file. I was recently asked how to reset the source code association

Using Set Next Statement to test code paths

Sometimes, it's the little things that make a big difference to my productivity. One of those little things is the addition of Set Next Statement (a.k.a. set instruction pointer / setip) support in the .NET Compact Framework v2. If you are not familiar

Just-In-Time Debugging on the .NET Compact Framework Version 2

In May, at MEDC 2005, I had the pleasure of debuting Just-In-Time debugging on the .NET Compact Framework version 2. Today's topic is based on my session. Mike Zintel 's MEDC post has some pictures from the conference. To enable Just-In-Time debugging,
Posted by DavidKlineMS | 4 Comments

Configuring How the Visual Studio Debugger Handles Custom Exceptions

A few days ago, I posted on how to configure the debugger to stop on first chance exceptions in Visual Studio .NET 2003 and Visual Studio 2005 . Today, I'd like to talk about how to configure the Visual Studio debugger for handling custom exceptions implemented
Posted by DavidKlineMS | 1 Comments
More Posts Next page »
 
Page view tracker