none
Windbg - Something weird comes out with !runaway 0x4

    Question

  • Hi,
    I am not sure if this is the correct sub forum for this kind of question.  I couldn't find a windbg forum.
    Please help move this thread. Thanks.
    A process crashed after running for 101 days.

    With !runaway 0x4 command, it shows there're 90 threads.

    But what weird is that 3 of these threads are shown to be there for 24692 days.
    I don't get it, 24692 days?

    Would this be a bug of windbg and dump?
    If it's a bug, how should I report to microsoft.

    0:081> !runaway 0x04
     Elapsed Time
      Thread       Time
      88:176c      24692 days 13:29:46.920
      90:152c      24692 days 13:29:46.889
      89:10d8      24692 days 13:29:46.889
       0:a44       101 days 19:08:52.094
       1:a3c       101 days 19:08:51.797
       2:a5c       101 days 19:08:47.563
       8:a84       101 days 19:08:47.016
       7:a80       101 days 19:08:47.016
       6:a78       101 days 19:08:47.016
       5:a74       101 days 19:08:47.016
       4:a6c       101 days 19:08:47.016
       3:a58       101 days 19:08:47.016
       ...
       ...
       ...


    Any suggestions? 
    Thanks.  
    Friday, September 14, 2012 2:16 AM

All replies