MSDN Magazine - September 2008 - (Page 25)

As a result, the IL offset in the P8 bucket will belong to the first managed frame in the calling AppDomain that sees the exception. Simply put, this will typically be an offset in the method where the AppDomain transition was initiated on the thread. A CLR host is able to retrieve the bucket parameters for the current exception on the thread by using the ICLRErrorReportingManager::GetBucketParametersForCurrentException hosting API. Finally, at this point you would typically see a dialog that will prompt you to debug or close the application. Clicking Close Program would terminate the process, while clicking on Debug would launch the managed just-in-time (JIT) debugger that is specified in the DbgManagedDebugger entry under the HKLM\Software\Microsoft\.NetFramework registry key. In the final step of the CLR’s unhandled exception process, the CLR will attempt to display details pertaining to the exception that went unhandled on the standard error console. Typically, you will see the managed stack trace dump. If the exception is a more serious one (such as a StackOverflowException or OutOfMemoryException), a simple string is displayed in the place of the stack dump. This is4:48:37because you may not done PM MSDN Swordfish Half Horz.ai 17/3/08 have enough stack to execute or memory to form the extensive The Watson buckets include details such as the module that was responsible for the crash or the IL offset at which the crash happened. stack trace to display on the console. If the CLR is not cautious in such a situation, it could run into a recursive exception scenario. Once the process is complete, the CLR’s unhandled exception processing mechanism returns control to its caller, which may be either the OS or the CLR itself. Future Concerns This column is based on the version of the CLR that ships with the .NET Framework 2.0 and thus may have touched on some implementation details that could possibly change in the future. However, my goal here wasn’t to have you focus on the implementation but rather help you to try and understand the bigger picture of unhandled exception processing. Now you should understand what constitutes unhandled exception processing, its dependencies, and how it relates to the OS UEF mechanism. This knowledge will help you design better exception handling strategies and diagnostics mechanisms in your applications for any unexpected crashes you may encounter. GAURAV KHANNA is a Software Development Engineer on the CLR team at Microsoft where he works on managed exception handling implementation and CLR Hosting. Get moving. Stay focused. Take control. Enterprise Architect from Sparx Systems redefines visual modeling with a huge set of built-in tools, technologies and capabilities, coupled with a lightweight footprint and great agility. With deep support for UML 2.1 and its related standards, Enterprise Architect 7.1 is the ideal tool to analyze, design, build and manage your next software project. Keep your project moving, keep your team focused and stay in total control. Visitmsdnmagazine.com sparxsystems.com for a free trial September 2008 25 http://sparxsystems.com http://sparxsystems.com

Table of Contents Feed for the Digital Edition of MSDN Magazine - September 2008

MSDN Magazine - September 2008 Contents Toolbox CLR Inside Out Data Points Advanced Basics Office Space Cutting Edge Hierarchy ID New Features for Microsoft SQL Server 2008 Prism Data Services Advanced WPF Test Run Security Briefs Foundations { End Bracket }

MSDN Magazine - September 2008

For optimal viewing of this digital publication, please enable JavaScript and then refresh the page. If you would like to try to load the digital publication without using Flash Player detection, please click here.