Welcome to MSDN Blogs Sign in | Join | Help

Browse by Tags

All Tags » 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

What is a Side Effect?

We've all heard the commercials or read the prescription information sheets describing the possible side effects of medications. The side effects described are typically negative (ex: upset stomach). There are other side effects of a more positive nature;
Posted by DavidKlineMS | 1 Comments
Filed under:

Command Line Debugging Revisited - Part 6: IL Debugging Commands

Dan Elliott recently posted about the IL OpCodes supported by the .NET Compact Framework . This got me inspired to talk about the IL debugging commands in the .NET Compact Framework MDbg extension (mdbgnetcf.dll). Commands dis[assemble] in[ext] is[tep]
Posted by DavidKlineMS | 2 Comments
Filed under:

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

Command Line Debugging Revisited - Part 4: Attaching to Processes

Being able to attach to a running process is a very powerful debugger feature. It is especially handy when the application is in the field. With the CorDbg debugger, formal attach to process support was not available when debugging .NET Compact Framework
Posted by DavidKlineMS | 4 Comments
Filed under:

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 3: Process Control

In the previous parts of this series, I talked about getting started with MDbg and using the Device Emulator . Today, I would like to talk about how to use MDbg to control processes on the device being debugged. Commands cp[roc] kp[roc] pro[cessenum]
Posted by DavidKlineMS | 4 Comments
Filed under:

Command Line Debugging Revisited - Part 2: The Device Emulator

The Visual Studio 2005 Device Emulator is a very cool tool for developing, testing and debugging Windows Mobile applications. You can design for and run on the wide variety of Windows Mobile devices. In addition, you can install and use the localized
Posted by DavidKlineMS | 3 Comments
Filed under:

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

MEDC 2006 Update: What went wrong in the debugging demo during APP326?

Ever since I finished my MEDC 2006 presentation (APP326 - Essential Tips and Tricks for .NET Compact Framework Application Developers), I have been bothered by the fact that one of my demos did not work 100% as I had designed and practiced. During the
Posted by DavidKlineMS | 1 Comments
Filed under: ,

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

What is a Race Condition?

I've been posting a bit, lately, on debugging multi-threaded applications. When talking about deadlocks , I mentioned that I was adding a Sleep statement to ensure that I hit the deadlock issue. The reason that I needed to force the deadlock was that,
Posted by DavidKlineMS | 1 Comments
Filed under:
More Posts Next page »
 
Page view tracker