windbg

I've got a process that is showing ~4,294,965,900 "current logical threads" (according to the performance counters) and ~400 physical threads. I've created a memory dump using ADPlus (-hang), and windbg (!threads) only shows me the physical threads. How do I find out where all these logical threads are coming from? How do I find out where all these logical threads are coming from? they aren't. They don't exist. You simply can't have 4 billion threads of any kind, unless you're running on a 64-bit machine with, oh, say a couple of petabyte of RAM at the very least . Every thread, whether it is

I have a situation where IE7 hangs accessing my web app. Based on the excellent suggestion from George V. Reilly , I installed WinDbg to download the IE symbols, setup Process Explorer to use those symbols, and then used Process Explorer to get a stack trace for the hung thread. I have pasted the stack trace below. Does someone more familiar with the IE internals have an idea of what is happening, or a suggestion on how to progress with this? ntkrnlpa.exe!KiUnexpectedInterrupt+0x8d ntkrnlpa.exe!PsDereferencePrimaryToken+0x362 ntkrnlpa.exe!KiDeliverApc+0xb3 ntkrnlpa.exe!KiDispatchInterrupt

I've got stuck in a problem with gflags when trying to find some memory leaks in a windows app. When I turn on the ust flag (in order to collect memory allocations stack traces) the memory of my application increases much faster than it does when the flag is off (it reaches to 800MB in 10 min aprox. which is far from the 50-100MB/day I get when the flag is off). I've read that there is a maximum for stack traces of 32MB, so I suppose this shouldn't be a problem. The computer is a 4x Intel(R) Xeon(R) CPU E5410 @ 2.33GHz . If someone could give me some hint I'd really appreciate it. Thank you!

I got a support email from a customer saying his app crashes when it starts and all he gets is a message like: (App Name) ran into a problem You can send info to Microsoft about what went wrong to help improve this app. Files that will be sent to Microsoft C:\Users\User_Name\AppData\Local\Temp\WER####.tmp.appcompat.txt C:\Users\User_Name\AppData\Local\Temp\WER####.tmp.hdmp I thought - Microsoft isn't going to help them really with my silly app. They should send the dump file to me for debugging, but how to do it? A sample dump file I got from a crashing app was 90MB and after zipping it is

.cmdtree 简介 使用形式 .cmdtree cmdfile 参数 cmdfile 命令文件，包含多个你需要的命令 使用步骤 1、使用命令创建文本文件CMDTREE.TXT，使用以下示例作为模板。您可以按所需方式修改{}之间的节： windbg ANSI Command Tree 1.0 title {"Common Commands"} body {"Common Commands"} {"Information"} {"Time of dump"} {".time"} {"Process being debugged"} {"|"} {"Dump Location"} {"||"} {"Create server on port 9999"} {".server tcp:port=9999"} {"Show remote connections"} {".clients"} {"Process Environment Block"} {"!peb"} {"Logging"} {"Open Log"} {".logopen /t /u /d"} {"Close Log"} {".logclose"} {"Modules"} {"All Modules"} {"lm D sm"} {"Loaded Modules"} {"lmo D sm"} {"Loaded Modules

dbgrpc.exe that comes with windbg does not seem to work well under Windows 7. I have followed the instructions, enabling RPC state information as stated in MSDN I created test out-of-proc COM server and client, run client under debugger, invoke COM server method (step into method before return) and run dbgrpc. I was able to enumerate the RPC endpoints. However, when I try to get thread info like such: dbgrpc -t -P 1234 Nothing useful was printed - just header without any data row: PID CELL ID ST PNO IFSTART THRDCELL CALLFLAG CALLID LASTTIME CONN/CLN I've fount information that other people