Click here to Skip to main content
Click here to Skip to main content
Technical Blog

Tagged as

Tips on Debugging : Using DebuggerHidden attribute

, 12 Sep 2010 CPOL
Rate this:
Please Sign up or sign in to vote.
How to use the DebuggerHidden attribute

DubuggerHidden attribute tells the Visual Studio debugger that the method is hidden from the debugging process and while debugging. This is quite helpful when you don't want to go to stepping inside of a method while debugging.

When you mark a method with DebuggerHidden() attributes, it explicitly tells the debugger not to step inside of that method and no break point will be hit over that method. Now I am going to explain the same using an example with Intellitrace debugging.

1

Let’s consider you have the below code snippet:

We have set two break points in each of the methods (Line 22, and Line 31 as shown). Now if you run this application and check the output intellitrace debugging window, you will get the below output:

3

As per the above image, you can see the flow of the application from Main() > Method1() > Method2(). If you also check the current live event’s “Call Stack”, that also represents the call of method2() from method1(). This is as per our expected behavior.

Now, if you don’t need to go inside Method1() while debugging and debugger should not stop inside method1() for any of the breakpoints, you have to add “DebuggerHidden()” attributes with the method1(). If you try to debug the application with the same breakpoint, CallStack() and IntelliTrace debugger view will be something different.

4

If you check the above image, the debugger reached Method2() through Method1(), but breakpoint in method1() never hits, because of the “DebuggerHidden” attribute.

If you move from “EventView” mode to “CallView” mode in Intellitrace window, you can find the actual flow of sequence of the program.

5

Summary

In this blog post, I have explained how we can hide a method from debugger to step in using “DebuggerHidden” attribute.

Hope this will help you.

My Other Articles on Debugging


Filed under: General, Tips and Tricks, Visual Studio 2010

License

This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Share

About the Author

Abhijit Jana
Technical Lead
India India
.NET Consultant | Former Microsoft MVP - ASP.NET | CodeProject MVP, Mentor, Insiders| Technology Evangelist | Author | Speaker | Geek | Blogger | Husband
 
Blog : http://abhijitjana.net
Web Site : http://dailydotnettips.com
Twitter : @AbhijitJana
My Kinect Book : Kinect for Windows SDK Programming Guide
Follow on   Twitter

Comments and Discussions

 
GeneralMy vote of 1 PinmemberArnaud Dovi31-May-12 6:52 
GeneralMy vote of 4 PinmemberOnskee110-Mar-11 9:40 
GeneralRe: My vote of 4 PinmvpAbhijit Jana10-Mar-11 12:06 
GeneralGreat One PinmentorBrij12-Sep-10 6:02 
GeneralRe: Great One PinmvpAbhijit Jana12-Sep-10 6:17 
GeneralCongrats!!! for the Half Century PinmentorKunalChowdhury12-Sep-10 1:05 
GeneralRe: Congrats!!! for the Half Century PinmvpAbhijit Jana12-Sep-10 3:41 
GeneralAwesome - Have 5 PinmentorKunalChowdhury12-Sep-10 1:02 
GeneralRe: Awesome - Have 5 PinmvpAbhijit Jana12-Sep-10 3:42 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.

| Advertise | Privacy | Terms of Use | Mobile
Web01 | 2.8.1411022.1 | Last Updated 12 Sep 2010
Article Copyright 2010 by Abhijit Jana
Everything else Copyright © CodeProject, 1999-2014
Layout: fixed | fluid