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

What's New — Wed, 17 Jun 2009 00:54:01 GMT

I know that for a lot of you this is a bit far into the future, but I thought it would be nice to run

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

kanchirk — Wed, 17 Jun 2009 03:53:07 GMT

Cool.. Nice intro write up. Looking forward for some great posts.

Thanks

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

Jack — Wed, 17 Jun 2009 04:37:23 GMT

Powerful! I think it will surely save us lots of time when debugging.

Daily tech links for .net and related technologies - June 16-18, 2009

Sanjeev Agarwal — Thu, 18 Jun 2009 09:31:13 GMT

Daily tech links for .net and related technologies - June 16-18, 2009 Web Development Revised: ASP.NET

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

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

Interesting Finds: 2009 06.15 ~ 06.21

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

WebNamedfunctionexpressionsdemystifiedProjectVoldemort-adistributedkey-valuestora...

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.

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

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

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.