First look at debugging .NET 4.0 dumps in Visual Studio 2010

re: First look at debugging .NET 4.0 dumps in Visual Studio 2010

Wajid Poernomo — Mon, 12 Nov 2012 04:41:40 GMT

I haven't found much information about lining up the source code with the crash dump, although it looked pretty straightforward in this article. I'm working with Silverlight hosted on my local dev machine with source code available, and did a crash dump from taskmanager on the IE process. I'm not able to see any method names or go to the source code from the process outlined in this article - would be great to see some more examples of how to line up with source code using Silverlight (currently ANTS profiler does not support this).

re: First look at debugging .NET 4.0 dumps in Visual Studio 2010

Tess1 — Thu, 04 Feb 2010 12:10:04 GMT

Hi Jimmy,

There are some caveats to debugging dumps in VS with asp.net in particular because aspx pages etc. are JIT compiled, which means that the dlls are recompiled and changed between runs.

That means that to look at an asp.net dump you can not have recompiled the app in between when it was taken and when you look at it if you want to see the .net calls. You should be able to see the function names for calls in compiled .net assemblies and framework assemblies fine though. For winforms its a different story since everything is compiled. Should also work i believe if you use precompiled asp.net apps.

re: First look at debugging .NET 4.0 dumps in Visual Studio 2010

Jimmy — Wed, 03 Feb 2010 15:25:43 GMT

Hi Tess,

I am a big fan of your blogs. It has helped me getting better understanding of CLR internals.

I have one question about debugging with VS 2010. I tried debugging lab 1 with VS2010 but when I open the dump file, I do not see any method namess in the thread stack, all I get is just the hex addresses. I have compiled buggybits with 4.0 but you also mentioned switching some setting in web.config. Can you elaborate what exaclty you changed in web.config because that's what I might be missing.

Thanks

re: First look at debugging .NET 4.0 dumps in Visual Studio 2010

bayrak — Thu, 09 Jul 2009 16:49:50 GMT

Introducing such a topic you'd like to congratulate you've let us know. Have good work.

re: First look at debugging .NET 4.0 dumps in Visual Studio 2010

Tess — Sun, 05 Jul 2009 21:27:14 GMT

Hi Ted and Jezz,

Ted, no, the dumps that are sent to MS when you click send report do not contain the loader heap and thus you can't resolve managed function names etc.

I think though that it does save off the dump on your harddrive as a .hdmp if you do want to look at it.

Jezz, here is how you load sos up in vs 2008,

http://blogs.msdn.com/tess/archive/2007/10/19/net-finalizer-memory-leak-debugging-with-sos-dll-in-visual-studio.aspx loading it up in 2010 should be very similar if not the same.

Thanks

Tess

re: First look at debugging .NET 4.0 dumps in Visual Studio 2010

Jezz — Sat, 04 Jul 2009 14:35:07 GMT

Hi Tess,

I love your blog, I dont do much debugging any more but this article really caught my eye. Can you do a post on loading sons of strike in VS2010? That sounds interesting!! As you've mentioned it would make developers feel more at home in VS than WinDbg.

With regards to Ted's post above, I think he (sorry we) want access to a hobbyist Microsoft Private Symbol Server and to see more than just function names.

re: First look at debugging .NET 4.0 dumps in Visual Studio 2010

Ted Howard — Fri, 03 Jul 2009 18:46:44 GMT

When a user hits a crash they get the "Send report to Microsoft?" dialog. If they click "Yes" does that include a managed memory dump? (I call this Watson below.)

It would be awesome if Microsoft made it trivial for hobbyist and startup developers to access this Watson data. I realize that there are issues with making this easy. Off the top of my head, the Watson website would need to scale up fast, ownership claims (authx) would be a real pain, and privacy/information-disclosure-threat issues would be painful.

On the same topic, I love the Windows 7 'bug report' wizard that helps the user take screenshots and records UI. Great stuff for developers means better software for users. Thanks, Microsoft.

Interesting Finds: 2009 06.15 ~ 06.21

gOODiDEA — Sun, 21 Jun 2009 05:50:00 GMT

WebNamedfunctionexpressionsdemystifiedProjectVoldemort-adistributedkey-valuestora...

Interesting Finds: 2009 06.15 ~ 06.21

gOODiDEA.NET — Sun, 21 Jun 2009 05:48:07 GMT

Web Named function expressions demystified Project Voldemort - a distributed key-value storage system

First look at debugging .NET 4.0 dumps in Visual Studio 2010 - Tess Ferrandez

DotNetShoutout — Thu, 18 Jun 2009 12:00:40 GMT

Thank you for submitting this cool story - Trackback from DotNetShoutout