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
The Beautiful Web
Jens Oliver Meiert • 2 votes
2
When your coding agent doesn’t understand your project, you’ll get junk
Benjamin Cane • 1 votes
3
LLM Use in the Python Source Code
Miguel Grinberg • 1 votes
4
Wagon’s algorithm in Python
John D. Cook • 1 votes
5
An example conversation with Claude Code
Dumm Zeuch • 1 votes