\ncsc \/debug+ test.cs
\nNow when you run it you should get an exception. Good! We now have a test subject!\n<\/p>\n
![\"crashandburn\"](\"https:\/\/blog.monnet-usa.com\/wp-content\/uploads\/2009\/06\/crashandburn.png\" "\\"crashandburn\\"")
<\/p>\n
Crash And Dump<\/h3>\n
To make this happen I first needed to get setup with all the necessary tools:<\/p>\n
- \n
- Install the Windows symbols package<\/a><\/li>\n
- Install the Windows Debugging tools<\/a><\/li>\n
- Add the location of the Windows Debugging tools to your Windows system PATH environment variable<\/li>\n<\/ol>\n
When you install the debugging tools, you get WinDbg the main Windows Debugger and ADPlus a script that will allow you to capture a crash and create a dump.
\nNow we can get started:<\/p>\n- \n
- Open a command window<\/li>\n
- Get ADPlus to start your application and create a dump by typing the following command:<\/br>
\nADPlus -crash -FullOnFirst -sc “C:Program FilesCrashAndBurntest.exe” -o “C:Program FilesCrashAndBurn”\n <\/li>\n - ADPlus will kick off your app as well as a command window, then will write out the crash dump to a new directory under the one specified in the “-o” parameter<\/li>\n
- Now navigate to the dump folder and check out its contents<\/li>\n
![\"Crash](\"https:\/\/blog.monnet-usa.com\/wp-content\/uploads\/2009\/06\/crashandburndumps-300x144.png\" "\\"crashandburndumps\\"")
Crash dumps<\/p><\/div>\n
- Now you can kick off WinDbg, then open the latest dump file<\/li>\n<\/ol>\n
![\"Crash](\"https:\/\/blog.monnet-usa.com\/wp-content\/uploads\/2009\/06\/windbgopencrashdump.png\" "\\"windbgopencrashdump\\"")
\nNow you’re ready to analyze the crash!<\/p>\nAnalyzing The Crash<\/h3>\n
Let’s run the following commands in WinDbg:
\n
\n.loadby sos mscorwks
\n!analyze -v
\n<\/code><\/p>\nThis will give us a starting point in terms of figuring out where the exception was.
\n![\"windbganalyzecrashdump\"](\"https:\/\/blog.monnet-usa.com\/wp-content\/uploads\/2009\/06\/windbganalyzecrashdump.png\" "\\"windbganalyzecrashdump\\"")
\nOf course you may have to do more “digging” for the root cause. Here is the output:\n<\/p>\n\r\n<\/pre>\n
Notice the following text inside the verbose output:<\/p>\n
\r\nException object: 013f4a94\r\nException type: System.InvalidCastException\r\nMessage: Unable to cast object of type 'C' to type 'A'.\r\nInnerException:
\r\nStackTrace (generated):\r\n SP IP Function\r\n 0012F418 00DC01F5 test!EntryPoint.DoSomething()+0x155\r\n 0012F480 00DC0088 test!EntryPoint.Main()+0x18\r\n<\/pre>\n This tells us that a cast exception occurred, which the exception that Trey wanted to intentionally trigger.<\/p>\n
\nTo learn more I recommend to look up Tess Ferrandez blog since she has a ton of details and some labs.\n<\/p>\n
References And Resources<\/h3>\n
These blogs and resources are all “must-read” and “must-bookmark”!<\/p>\n
- \n
- “If broken it is, fix it you should” blog by Tess Ferrandez on MSDN<\/a><\/li>\n
- “Capturing ADPlus CLR Crashes” by Trey Nash on MSDN<\/a><\/li>\n
- Windows Debugging Tools home page on MSDN<\/a><\/li>\n
- ADPlus Command-Line Options on MSDN<\/a><\/li>\n
- SOS Debugging Options<\/a><\/li>\n
- WinDbg \/ SOS Cheat Sheet<\/a><\/li>\n
- Common WinDbg Commands from windbg.info<\/a><\/li>\n<\/ol>\n","protected":false},"excerpt":{"rendered":"
Managed Code Makes Us Forget The Bad Ol’ Days Of Crashes In the late eighties, during and after college, I earned my basic debugger stripes by analyzing mainframe cobol stack dumps and DOS\/C++ debugging (on a French videotext server product). Thank God for me, my passion was Smalltalk and then later other now traditional virtual […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4],"tags":[],"class_list":["post-95","post","type-post","status-publish","format-standard","hentry","category-tools"],"_links":{"self":[{"href":"https:\/\/blog.monnet-usa.com\/index.php?rest_route=\/wp\/v2\/posts\/95","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.monnet-usa.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.monnet-usa.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.monnet-usa.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.monnet-usa.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=95"}],"version-history":[{"count":33,"href":"https:\/\/blog.monnet-usa.com\/index.php?rest_route=\/wp\/v2\/posts\/95\/revisions"}],"predecessor-version":[{"id":133,"href":"https:\/\/blog.monnet-usa.com\/index.php?rest_route=\/wp\/v2\/posts\/95\/revisions\/133"}],"wp:attachment":[{"href":"https:\/\/blog.monnet-usa.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=95"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.monnet-usa.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=95"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.monnet-usa.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=95"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
- “Capturing ADPlus CLR Crashes” by Trey Nash on MSDN<\/a><\/li>\n
- Now you can kick off WinDbg, then open the latest dump file<\/li>\n<\/ol>\n
- Install the Windows Debugging tools<\/a><\/li>\n