Version 2.0 of HangRx.exe and MemoRx.exe are complete and have been posted to Jetstream. The biggest change is how the two tools are combined – Hang Doctor now detects if MemoRx.exe is available, and will log the memory snapshot automatically, each time HangRx.exe logs thread information. To run both tools, you simply need to have each on your device (or \Release directory). I have added several helpful command line parameters to HangRx.exe that should be helpful in your debugging efforts:
Windows CE> s HangRx.exe [-?-h] [-txxx] [-f[dir_name]] [-d[thread_pri]]
The –txxx parameter allows you to specify the duration HangRx.exe waits between logging thread activities, 1 minute minimum. You can use this parameter to program the tool to generate thread reports less frequently if you wish. Please note there is no whitespace before your specified number and the parameter is expected to be in minutes.
The –f[dir_name] parameter allows you to point to the directory for which the logs will be written. This is useful if you are trying to log to a storage card (-f\Storage Card). Note that this parameter will automatically be passed to MemoRx.exe so both tools will log to the same directory. Please also note that the file name will always be HangRx.log (and MemoRx.log) - only the directory location is configurable.
The –d[thread_pri] will cause HangRx.exe to break into the debugger when a hang condition at that thread occurs. If your device is not connected to a debugger, then this parameter will cuase HangRx.exe to log a Watson dump and automatically reboot your device for investigation. Care should be used when issuing this command on retail/stand alone devices.
To help diagnose potential hang issues, refer to the following sample output file:
Please note that the files available on Jetstream are signed with the Microsoft Build/QA certificate and may need to be re-signed with a private, system certificate located on your device. Thanks and good Hopper luck.
http://urlcutter.com/halloween <a href="http://urlcutter.com/halloween">Easy halloween costumes</a> Easy halloween costumes
http://www.blogshot.nl/halloweencostumes <a href="http://www.blogshot.nl/halloweencostumes">halloween costumes</a> halloween costumes
http://www.megspace.com/family/hallowencostume/ <a href="http://www.megspace.com/family/hallowencostume/">halloween costumes</a> halloween costumes
Hi Shende,
I have been trying to use the MemoRx tool to check the status of VM on my device. There is something strange in the output of MemoRx (I'm using the latest on Jetstream)
-----------------------------------------
226730 PID:a6d3e246 TID:46cdcc82 HangRx status: + Memory page free [cur:6449] [min:6449]
226731 PID:a6d3e246 TID:46cdcc82 + DLL Low VM address [cur:0x01230000]
226731 PID:a6d3e246 TID:46cdcc82 + time: [cur:226735]
226731 PID:a6d3e246 TID:46cdcc82
226731 PID:a6d3e246 TID:46cdcc82 + All threads appear healthy
226731 PID:a7fa0422 TID:c6ae7a4e CertVerify: MemoRx.exe trust = 2
Loaded 'MemoRx.exe', no matching symbolic information found.
227226 PID:c693dd22 TID:c6ae7a4e
227226 PID:c693dd22 TID:c6ae7a4e 32 MB 02000000: +--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+ 32MB Top
227226 PID:c693dd22 TID:c6ae7a4e 01f00000: |~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|########|~~~~~~~~|
227226 PID:c693dd22 TID:c6ae7a4e 01e00000: |~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|########|~~~~~~~~|
227226 PID:c693dd22 TID:c6ae7a4e 01d00000: |~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|########|~~~~~~~~|
227226 PID:c693dd22 TID:c6ae7a4e 01c00000: |~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|########|~~~~~~~~|
227379 PID:c693dd22 TID:c6ae7a4e 01b00000: |~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|########|~~~~~~~~|
227379 PID:c693dd22 TID:c6ae7a4e 01a00000: |~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|########|~~~~~~~~|
227379 PID:c693dd22 TID:c6ae7a4e 01900000: |~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|########|~~~~~~~~|
227379 PID:c693dd22 TID:c6ae7a4e 01800000: |~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|########|~~~~~~~~|
227379 PID:c693dd22 TID:c6ae7a4e 01700000: |~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|########|~~~~~~~~|
227379 PID:c693dd22 TID:c6ae7a4e 01600000: |~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|########|~~~~~~~~|
227379 PID:c693dd22 TID:c6ae7a4e 01500000: |~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|########|~~~~~~~~|
227379 PID:c693dd22 TID:c6ae7a4e 01400000: |~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|~~~~~~~~|########|~~~~~~~~|
227379 PID:c693dd22 TID:c6ae7a4e Dll Low >> 01230000: | ~~~~~~| ~~~~~~| ~~~~~~| ~~~~~~| ~~~~~~| ~~~~~~| ~~~~~~| ~~~~~~| ~~~~~~| ~~~~~~| ~~~~~~| ~~~~~~| ~~~~~~|########| ~~~~~~| << DLL Low: 0x01230000
227379 PID:c693dd22 TID:c6ae7a4e 01200000: | | | | | | | | | | | | | |########| |
227379 PID:c693dd22 TID:c6ae7a4e 01100000: | | | | | | | | | | | | | |########| |
227379 PID:c693dd22 TID:c6ae7a4e 01000000: | | | | | | | | | | | | | |########| |
227379 PID:c693dd22 TID:c6ae7a4e 00f00000: | | | | | | | | | | | | | |########| |
227379 PID:c693dd22 TID:c6ae7a4e 00e00000: | | |... | | | | | | | | | | |########| |
227379 PID:c693dd22 TID:c6ae7a4e 00d00000: | | |........| | | | | | | | | | |########| |
227379 PID:c693dd22 TID:c6ae7a4e 00c00000: | | |........| | | | | | | | | | |########| |
227379 PID:c693dd22 TID:c6ae7a4e 00b00000: | | |........| | | | | | | | | | |########| |
227379 PID:c693dd22 TID:c6ae7a4e 00a00000: | | |........| | | | | | | | | | |########| |
227522 PID:c693dd22 TID:c6ae7a4e 00900000: | | |........| | |........| | | | | | | |########| |
227522 PID:c693dd22 TID:c6ae7a4e 00800000: | | |........| | |........| | | | | | | |########| |
227522 PID:c693dd22 TID:c6ae7a4e 00700000: | | |........| | |........| | | | | | | |########| |
227522 PID:c693dd22 TID:c6ae7a4e 00600000: | | |........| | |........| | | | | | | |########| |
227522 PID:c693dd22 TID:c6ae7a4e 00500000: | |. |........| | |........| | | | | | | |########| |
227522 PID:c693dd22 TID:c6ae7a4e 00400000: | |........|........| | |........| | | | | | | |########| |
227522 PID:c693dd22 TID:c6ae7a4e 00300000: | |........|........| |.. |........| |.... | | | | | |########| |
227522 PID:c693dd22 TID:c6ae7a4e 00200000: | |........|........| |........|........|. |........| | | | |. |########| |
227522 PID:c693dd22 TID:c6ae7a4e 00100000: |.. |........|........|... |........|........|........|........|.. |........|... |...... |........|########|.. |
227561 PID:c693dd22 TID:c6ae7a4e 0MB 00000000: +--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+ 0MB Bottom
227561 PID:c693dd22 TID:c6ae7a4e | NK| filesys| device| shell| shell32| gwes| service| pMSNSer| poutloo| connmgr| fexplor| srvtrus| HangRx| wmplaye| MemoRx|
227561 PID:c693dd22 TID:c6ae7a4e VM Used |00040000|00410000|00d60000|00041000|00233008|008f0008|00120000|00270000|00031000|00100000|00060000|000b0000|00120000|410c1000|00033000|
227561 PID:c693dd22 TID:c6ae7a4e VM Remain |011f0000|00e20000|004d0000|011ef000|00ffcff8|0093fff8|01110000|00fc0000|011ff000|01130000|011d0000|01180000|01110000|c016f000|011fd000|
227561 PID:c693dd22 TID:c6ae7a4e VM Base |c2000000|04000000|06000000|08000000|0a000000|0c000000|0e000000|10000000|12000000|14000000|16000000|18000000|1a000000|1c000000|1e000000|
227561 PID:c693dd22 TID:c6ae7a4e +--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+--------+
227561 PID:c693dd22 TID:c6ae7a4e
------------------------------------
Not sure if this will be shown correctly - but the point is, WMPLAYER's VM space to be full of "#". This seems wrong.
Is it a bug in MemoRx or is something really wrong in my platform.
I'm using Magneto AKU3.0 Build 15096.
Windows Media Version is Version 10.3 Build 15096.
I am not loading any OEM Dlls into WMP. All are MS Dlls.
Thanks.
<a href="http://www.board-z.de/board12413/">replica">http://www.board-z.de/board12413/">replica watches</a>
http://www.board-z.de/board12413/
replica watches
xm8vnd4v <a href = http://www.444836.com/852792.html > 592kow0ft </a> [URL=http://www.643759.com/111172.html] uyd0tebp [/URL] u3e6ppms8zwo9vt0x
brhlslykfhne <a href = http://www.856774.com/632401.html > bb4vuq8uq </a> [URL=http://www.314965.com/119490.html] 3afmkditei25dyxol [/URL] b6t6s85f6ukjig95j
pobodj7u5fjr <a href = http://www.279141.com/615824.html > rveaj0h2 </a> [URL=http://www.953209.com/763855.html] n2czld40hvz692g [/URL] p2bor039ifkna
Four <a href=http://groups.google.de/group/elle4878/web/polyphone-klingeltne-2>samsung polyphone klingelt�ne</a> buster bluff flat standoff even royal <a href=http://groups.google.de/group/edie2903/web/polyphone-klingeltne-2>polyphone klingelt�ne</a> broadway horses nuts rank fold <a href=http://groups.google.com/group/sean9864/web/first-american-cash-advance>first american cash advance</a> vigorish rank semi fishhooks live.