Things change and as I always say “that’s better than the alternative”. Although I have yet to put my finger on it, the behavior I experience when debugging Core applications is different than those which have come before. If I ever do figure out the specifics of those differences, I will write them down and […]
Read More →Tags: WinDbg
Find method parameters with WinDbg
I wrote this article, see the bottom where I do the memory dump analysis and wanted to expand on it some. Simply, if you are running managed code then you can decompile the source and see what the value of the Int32 passed to the Sleep() method, Figure 1. I explained how to save the […]
Read More →How to get computer name, host name from a memory dump, WinDbg
It is very important to have some back ground on what was happening when the memory dump was taken. This helps you detemermin which WinDbg commands to execute and provides you some context on how to interpret the output of those commands. I wrote this article here which explain my favorite WinDbg commands. I was […]
Read More →Object reference not set to an instance of an object
Just documenting something I did today. I was receiving the error shown in Figure 1. “??? has encountered an unexpected error: The requested action could not be completed. Details: Object reference not set to an instances of an object.” Figure 1, Object reference not set to an instances of an object exception I needed to […]
Read More →Capture a StackOverflowException and make a dump 0xc00000fd
I read in this article that “Starting with the .NET Framework 2.0, you can’t catch a StackOverflowException object with a try/catch block, and the corresponding process is terminated by default. Consequently, you should write your code to detect and prevent a stack overflow.” That is the reason why the following code was crashing my process […]
Read More →How to capture an ASP.NET Core memory dump on Azure App Service
I have written numerous articles about ASP.NET and creating memory dumps, but noticed I had not written one specifically about capturing an ASP.NET Core memory dump on an Azure App Service. Here are some of my ‘related’ articles of this matter. Create a memory dump for your slow performing Web App How to take a […]
Read More →What do C# values look like in WinDbg
One of the important areas you need to master when analyzing memory dumps is to recognize patterns that are normal and not normal. You can only come to those conclusions after looking at many, many, many, many memory dumps and either remembering or taking notes on how a process looks when all is ok, so […]
Read More →Dumping modules from a memory dump for decompilation, decompile
One of my favorite WinDbg commands is the psscor4 SaveAllModules (sam). I used to just bang that one out and use JustDecompile to look at the code to find out what was going on, like why the process was hanging or consuming more memory than expected. At the moment psscor4 does not support the most […]
Read More →Must use, must know WinDbg commands, my most used
I like to write stuff. As I personally use it for reference, instead of keeping it to myself, I often post it onto my blog here. Here is my list of most used WinDbg commands and what information I get for them. I was a big fan of PSSCOR, but since MEX is now a […]
Read More →MEX Debugging Extension for WinDbg
This has been my favorite WinDbg extension for a long time and I am very happy to see that it has been made public. It can be downloaded from here. To load the MEX extension, copy the MEX.DLL into the winext directory under which your WinDbg client is running. It can be placed any where […]
Read More →