process loops but 'context' doesn't show me where it loops 
Author Message
 process loops but 'context' doesn't show me where it loops

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.


Sun, 29 Aug 2004 17:23:50 GMT  
 process loops but 'context' doesn't show me where it loops
Did you try "~*kp"? That lists all threads' stacks.
Do you have symbols for your files (and the os)?


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.



Mon, 30 Aug 2004 05:54:22 GMT  
 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.



Mon, 30 Aug 2004 15:23:14 GMT  
 
 [ 3 post ] 

 Relevant Pages 

1. (Newbie) My Loop Isn't Looping - Aargh!

2. FOR loop doesn't end

3. fgets with stdin doesn't loop correctly

4. Curious 'while' loop

5. 'C', is it's grammar context sensit

6. Looping decision accepting 'Y' or 'N' only

7. program doesn't see '\0'

8. newbie's answer to two nested for loops question

9. Loop logic isn't working correctly

10. newbie's answer to two nested for loops problem

11. for loop can't get it working right

12. why won't msvc unroll loops?

 

 
Powered by phpBB® Forum Software