Re: Question -- Is there a bug in SOS u command??

I get the same and usually just hit CTRL-C to end the output.

However, the default ``u'' unassemble command can usually be coupled with an
address-range (limits the dump to the specified memory address). The SOS
(!sos.u) equivalent doesn't seem to care about address-range arguments.

I have been using the default with an address-range, which gives basically
the same disassembled output, but no debugging augmentation. You will get
something like this:

0>u <address> L50   (dump 50 instructions please)
...
03592dd2 b854376a07  mov     eax,0x76a3754
03592dd7 ff10        call    dword ptr [eax]
...

Instead of this:

0>!sos.u <address>
...
03592dd2 b854376a07  mov     eax,0x76a3754
03592dd7 ff10        call    dword ptr [eax]
System.Console[mscorlib.dll].WriteLine)
...

Check the debugger.chm file (found in the Windbg directory) for a more
detailed address-range illustration. 

-Joel.

-----Original Message-----
From: Discussion of the Rotor Shared Source CLI implementation
[mailto:[email protected]] On Behalf Of Zhao, Hai
Sent: Monday, July 07, 2003 11:11 AM
To: [email protected]

When I use SOS u command to print JITted method, for example,  

0:000> !name2ee iserializable.exe SimpleGraph.Main
--------------------------------------
MethodDesc: 7b50b8
Name: [DEFAULT] Void SimpleGraph.Main(SZArray String)

0:000> !u 7b50b8

SOS should print a code segment of JITted method, but in fact it seems
there is a dead loop, the console can't stop printting the code.

Is there anyone know this problem??

Thanks


Hai