CodeGuru Home VC++ / MFC / C++ .NET / C# Visual Basic VB Forums Developer.com
Results 1 to 1 of 1
  1. #1
    Join Date
    Jul 2001
    Sunny South Africa

    .NET Framework CLR Tools: How do I use the Microsoft CLR Debugger?

    Q: How do I use the Microsoft CLR Debugger?

    A: The Microsoft CLR Debugger is intended as an interim tool for debugging applications written and compiled for the common language runtime. The Microsoft CLR Debugger, and the accompanying documentation, is based on work being done for the Microsoft Visual Studio .NET debugger. As a result, the documentation refers mostly to the Visual Studio debugger rather than to the Microsoft CLR Debugger. In most cases, the information is applicable to both debuggers. However, you will find sections of the documentation describing some features that are not implemented in the Microsoft CLR Debugger (see the next paragraph). You can simply ignore these features and sections.

    • What are the main differences between the Microsoft CLR Debugger tool and the Visual Studio Debugger?

      • The Microsoft CLR Debugger does not support the debugging of Win32 native code applications. Only applications written and compiled for the common language runtime can be debugged with the Microsoft CLR Debugger.

      • Remote debugging is not implemented in the Microsoft CLR Debugger. The Registers window is implemented in the Microsoft CLR Debugger, but no register information appears in the window. Other operations that involve registers or pseudoregisters, such as displaying or changing a register value, are not supported.

      • The Disassembly window is implemented in the Microsoft CLR Debugger but shows the disassembly code that would be generated for the application if it were compiled as Win32 native code rather than .NET runtime code.

      • The Microsoft CLR Debugger does not support F1 help

    • What is Microsoft CLR Debugger Solution Model?

      The Microsoft CLR Debugger uses solutions to associate source files and the applications being debugged. A solution is created automatically when you open a compiled application and its associated source file or files. The next time you debug the same application, you can open the solution instead of having to load the source file and the compiled application separately.

    • How do I Use the Microsoft CLR Debugger (DbgCLR.exe)?

      To open an application for debugging (the first time):

      1. Start the CLR Debugger; run 'DbgCLR.exe', which is in the 'GuiDebug' directory of your .NET Framework installation.

      2. From the Debug menu, select 'Program to Debug'.

      3. In the 'Program to Debug' dialog box, go to the 'Program' box and click the ellipsis button (...). The 'Find Program to Debug' dialog box appears.

      4. Navigate to the directory containing the application you want to debug and select it.

      5. Click Open. This takes you back to the 'Program to Debug' dialog box. Notice that the working directory has been set to the directory containing your application.

      6. In the 'Arguments' box, type any arguments that your application requires.

      7. Click OK.

      8. From the 'File' menu, choose 'Open', then click 'File'.

      9. In the 'Open File' dialog box, choose the source file you want to open.

      10. Click OK.

      11. To open additional source files, repeat steps 8-10.

    • To open an existing solution

      1. From the 'File' menu, choose 'Open'.

    Last edited by Andreas Masur; December 22nd, 2005 at 05:00 PM.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts

Windows Mobile Development Center

Click Here to Expand Forum to Full Width

On-Demand Webinars (sponsored)

We have made updates to our Privacy Policy to reflect the implementation of the General Data Protection Regulation.