Maarten Balliauw • 3/15/2017

Using dotPeek to figure out why IIS crashed

Read Original

The article details a technical investigation where the author uses JetBrains dotPeek to provide symbols and decompiled source code for a crashed IIS application. Using a captured crash dump in Visual Studio, they identify a stack overflow exception caused by recursive calls to a TelemetryService method, demonstrating a real-world debugging workflow for a .NET application failure.

0 comments
#debugging #Dotnet #Ii
Using dotPeek to figure out why IIS crashed

Comments

No comments yet

Be the first to share your thoughts!

Browser Extension

Get instant access to AllDevBlogs from your browser

Top of the Week

1
Quoting Thariq Shihipar
Simon Willison • 2 votes
2
Top picks — 2026 January
Paweł Grzybek • 1 votes
3
In Praise of –dry-run
Henrik Warne • 1 votes
4
Deep Learning is Powerful Because It Makes Hard Things Easy - Reflections 10 Years On
Ferenc Huszár • 1 votes
5
Vibe coding your first iOS app
William Denniss • 1 votes
6
AGI, ASI, A*I – Do we have all we need to get there?
John D. Cook • 1 votes