process loops but 'context' doesn't show me where it loops
1. Make sure you're using good OS symbols. Your code
might be somewhere on the stack, but you might not see
it because the stack trace is incomplete.
2. Use pstat.exe (from SDK) or !runaway extension in
windbg to pinpoint the thread that consumes the CPU.
Quote:
> Hi!
> I have a process (my own) that loops and burns 100% of the
> CPU. I attached the de{*filter*} to that process and did
> a 'break'. In the context drop down list I try to get the
> functions which is in a loop. I tried that in all the
> running threads but in the 'context'-list I can only see
> NTDLL! and KERNEL32!. I repeated the whole procedure
> multiple times but I never see any other calls than NTDLL
> and KERNEL32. Since my process is in a 100% loop I
> expected to see one of my functions in the context. I also
> tried to use the latest version of WinDbg (which is great)
> but the results were the same.
> If you have any clue, please let me know.
> Thanks.
> Olaf.
