windbg

I have a .NET windows service application with a memory leak. Overview: The service connects to another service via TCP, and writes data to a SQL server database. The service normally runs between 100 and 300 MB depending on how much data it has queued up. It generally takes 3 + days before I noticed the service's memory is getting out of hand, and will have a Out Of Memory exception within 2 weeks of running. I think the issue might be related to a massive number of objects that are not leaving the finalization queue. I have attached to the service with Windbg and run the !FinalizationQueue

I work on a large application, and frequently use WinDbg to diagnose issues based on a DMP file from a customer. I have written a few small extensions for WinDbg that have proved very useful for pulling bits of information out of DMP files. In my extension code I find myself dereferencing c++ class objects in the same way, over and over, by hand. For example: Address = GetExpression("somemodule!somesymbol"); ReadMemory(Address, &addressOfPtr, sizeof(addressOfPtr), &cb); // get the actual address ReadMemory(addressOfObj, &addressOfObj, sizeof(addressOfObj), &cb); ULONG offset; ULONG

I have some code in C# and C++ ( in one project ). This code have some crash and i trying t find it. but this crash is not reproduce any time - and i can't find it. I want to configure the code / the windows OS to create dump file on the crash. the limitation that i have are ... I have limited access to the machine that this crash reproduce on - this is not developing machine .. this is testing Lab machine So, How to do it ? How can i change the properties in the solution that a new dump file will created on any crash? (the aim is to be able to analyze the dump in the windbg tool) I find it

I used to debug the Windows Kernel using VirtualKD , WinDBG and a single Virtual Machine. Recently I got a Linux machine, and now I wonder- What's the easiest way to debug the Windows Kernel when your host is unable to run VirtualKD/WinDBG* ? I assume the solution will require two Virtual Machines, but I rather have two instances hosted on my actual machine rather than having an instance residing inside another virtual instance... Is there anyway to make that work? Thanks in advance! *Wine is the last resort for stability reasons... Solved! Basically, I ended up using two (VirtualBox) VMs

可以将文章内容翻译成中文,广告屏蔽插件可能会导致该功能失效(如失效，请关闭广告屏蔽插件后再试): 问题: I've spent several days trying to speed up loading of symbols when debugging crash dumps using WinDbg , and I'm unable to get past a particular problem. The issue is that when symbols for a module in the dump doesn't exist in any accessible symbol store or symbol server location (e.g. it's a third-party modules without available symbols), WinDbg will spend literally hours looking for them. I've set up my symbol path correctly to properly set the search order and the cache directories: .sympath cache*C:\SymbolCache1;\\our.corp\SymbolStore;SRV