I have a mixed-mode C++/CLI application which uses WPF. Crashes from our customers are reported as minidumps to our own server.
I am just having hard time understanding the difference between virutal memory vs physical memory leak from debugging .net application perspective.
I amtrying the code sample provided at Naveen\'s blog at http://naveensrinivasan.com/2010/06/11/piracy-in-net-code-%e2%80%93-part-3-%e2%80%93-even-when-the-code-is-obfuscated/.
I have created a dump using clrdump.When I go to view it using sos, I load up sos and then run !dso, but the error I get is:
I am trying to understand information stored in the method table. Here is my code. class MyClass { private int x = 60;
I\'m new to WinDBG.I\'m looking for the cause of a memory leak and I\'ve got as far as my current knowledge can take me.
I have a memory dump that I\'m using to troubleshoot a client issue.This is a .NET (C#) application.The problem with my application is that too many instances of a particular class are being created.T
What does it mean if !gcrootreturns an empty thread list? 0:000> !gcroot 0000000010817c50 Note: Roots found on stacks may be false positives. Run \"!help gcroot\" for
So if you want to look at sync block for an object, under sos you have to look at -4 bytes (on 32 bit machines) before the object address. Does anyone know what is the wisdom for going back 4 bytes? I
Is it possible to attach Windbg to a Silverlight based application running under internet explorer ( or any other browser)? If its possible, then will I have to attach windbg to the brow开发者_JAVA百科