windbg调试系列教程：sos扩展的介绍和使用

博客 分享
0 256
张三
张三 2022-02-22 22:55:43
悬赏：0 积分 收藏

windbg调试系列教程：sos扩展的介绍和使用

SOS是什么？

直观来说，sos就是一个程序集文件。这个程序集的作用就是让我们在使用windbg分析.net进程时，更加方便快捷。通过sos，我们可以清晰的查看CLR运行时的各类信息，辅助我们去理解托管内存的状态和含义。

这个程序集是随.NET Framework一起安装的，一般不需要单独安装。在我本机自动安装的位置如下：

C:\Windows\Microsoft.NET\Framework\v4.0.30319\SOS.dllC:\Windows\Microsoft.NET\Framework64\v4.0.30319\SOS.dll

 

如何加载和使用

一般情况，使用windbg自带的命令【.loadby sos clr】即可自动加载，使用【.chain】查看加载是否成功。

0:098> .loadby sos clr0:098> .chainExtension DLL search Path:    ....省略....Extension DLL chain:    ....省略....    C:\Windows\Microsoft.NET\Framework64\v4.0.30319\sos.dll: image 4.8.9014.0, API 1.0.0, built Tue Oct 12 08:17:44 2021        [path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\sos.dll]    ....省略....

此扩展提供的所有命令格式均为：![command] [options]，下面就根据命令作用分类，讲解重要且常用的命令。

查看线程的命令

  1. Threads命令
    • 作用：输出全部托管线程信息
    • Threads [-live] [-special]
      • 默认输出常规的工作线程信息
      • -live 只输出存活的线程
      • -special 只输出特殊线程信息，包含：GC线程、debugger辅助线程、finalizer线程、AppDomain unload线程、线程池定时器线程
    • 输出示例和解读：
    • 查看代码
      0:015> !ThreadsThreadCount:      4UnstartedThread:  0BackgroundThread: 3PendingThread:    0DeadThread:       0Hosted Runtime:   no                                                                                                        Lock         ID OSID ThreadOBJ           State GC Mode     GC Alloc Context                  Domain           Count Apt Exception   0    1 5320 0000024cdf5efd80    26020 Preemptive  0000024CE14ECC50:0000024CE14EDC30 0000024cdf5c4cf0 0     STA    5    2 7c74 0000024cdf618df0    2b220 Preemptive  0000000000000000:0000000000000000 0000024cdf5c4cf0 0     MTA (Finalizer)   15    3 5844 0000024cfedca6a0  3029220 Preemptive  0000024CE14CA048:0000024CE14CBC30 0000024cdf5c4cf0 0     MTA (Threadpool Worker)   16    4 7dc0 0000024cfed99a20  1029220 Preemptive  0000024CE14CBF38:0000024CE14CDC30 0000024cdf5c4cf0 0     MTA (Threadpool Worker)      0:098> !Threads -special                OSID Special thread type        1 27d3c DbgHelper         2 22954 GC         3 2b168 GC         4 c478 GC         5 13778 GC         6 62ec GC         7 2dd1c GC         8 ec60 GC         9 138b8 GC        10 e988 Finalizer        11 9850 ProfilingAPIAttach        16 180c Timer        17 24960 ThreadpoolWorker        18 e70c ThreadpoolWorker        20 29e94 GC        21 2abdc GC        22 2d760 GC        23 22ad8 GC        24 2d288 GC        25 9750 GC        26 52e8 GC        27 2b9a4 GC        29 18340 Wait        ....省略....
    • 空列 ID OSID：前三列分别是windbg自定义的线程序列、CLR线程ID、OS线程ID。XXXX代表线程已Dead。
    • ThreadOBJ是线程的对象地址
    • Domain列代表当前线程所在的AppDomain，Lock Count列代表当前线程持有的锁数量，
    • APT列代表线程的COM模式，有MTA、Ukn等值，能区分线程类型(Finalizer\Threadpool Worker\Threadpool Completion Port等)
    • Exception列表示对应线程最新的异常对象。
  2. ThreadState命令
    • 作用：查看线程状态。
    • ThreadState < State value field >，参数就是上个命令输出的state值。
    • 输出示例和解读：
    • 0:015> !ThreadState 1029220    Legal to Join    Background    CLR Owns    In Multi Threaded Apartment    Fully initialized    Thread Pool Worker Thread
    • 表明这是后台线程、属于CLR、初始化完成、是线程池工作线程。
  3.  ThreadPool命令
    • 作用：查看线程池信息。此命令没有额外的控制选项。
    • 输出示例和解读：
    • 0:001> !threadpoolCPU utilization: 32%Worker Thread: Total: 183 Running: 154 Idle: 29 MaxLimit: 1000 MinLimit: 100Work Request in Queue: 0--------------------------------------Number of Timers: 1--------------------------------------Completion Port Thread:Total: 10 Free: 6 MaxFree: 16 CurrentLimit: 6 MaxLimit: 200 MinLimit: 20
    • 各项信息比较清楚，按照需要查看即可。

查看堆栈类的命令

  1. clrstack命令：
    • 作用：查看当前线程的托管堆栈
    • CLRStack [-a] [-l] [-p] [-n]
      • -p：输出内容包含堆栈中的方法入参
      • -l：输出内容包含堆栈中的方法的局部变量
      • -a：等效同时使用-p和-l
      • -n：输出内容不包括源码文件信息和行号。
    • 输出示例和解读：
    • 查看代码
      0:015> !clrstack -n -aOS Thread Id: 0x759c (15)        Child SP               IP Call Site0000005c65ffef48 00007ffc73b82f14 [HelperMethodFrame: 0000005c65ffef48] System.Threading.Thread.SleepInternal(Int32)0000005c65fff040 00007ffc5988b78b System.Threading.Thread.Sleep(Int32)    PARAMETERS:        millisecondsTimeout = <no data>0000005c65fff070 00007ffbfc3c946b Tccc.WindbgDemoAPP.MainWindow+c.b__22_0(System.Object)    PARAMETERS:        this (0x0000005c65fff0a0) = 0x0000023f431ffd68        a (0x0000005c65fff0a8) = 0x00000000000000000000005c65fff0a0 00007ffc59853480 System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)    PARAMETERS:        executionContext = <no data>        callback = <no data>        state = <no data>        preserveSyncCtx = <no data>    LOCALS:        <no data>        <no data>        <no data>0000005c65fff170 00007ffc59853305 System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)    PARAMETERS:        executionContext = <no data>        callback = <no data>        state = <no data>        preserveSyncCtx = <no data>0000005c65fff1a0 00007ffc5987a506 System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()    PARAMETERS:        this = <no data>    LOCALS:        <no data>0000005c65fff1e0 00007ffc59879746 System.Threading.ThreadPoolWorkQueue.Dispatch()    LOCALS:        0x0000005c65fff230 = 0x0000023f431ffdc0        0x0000005c65fff25c = 0x000000002019e530        0x0000005c65fff258 = 0x0000000000000001        <no data>        0x0000005c65fff228 = 0x0000023f43201cb0        <no data>        0x0000005c65fff244 = 0x0000000000000000        <no data>        <no data>0000005c65fff678 00007ffc5b927873 [DebuggerU2MCatchHandlerFrame: 0000005c65fff678]
    • IP列代表当前方法的代码地址入口，通过!U命令可以查看IL代码和汇编代码。Call Site列就是堆栈方法信息。
    • PARAMETERS和LOCALS分别代表对应方法的入参和局部变量。其中入参可以正常显示名称，但是局部变量没有实际变量名称，而是通过变量地址来表示：<local address> = <value>。
  2. dumpstack命令
    • 作用：查看线程的完整堆栈信息（包含托管、非托管）
    • DumpStack [-EE] [-n] [top stack [bottom stack]]
      • -ee：只显示托管代码的堆栈信息
      • -n：同上，输出信息屏蔽掉源码文件信息和行号
    • 输出示例和解读：
    • 查看代码
      0:015> !dumpstack -eeOS Thread Id: 0x759c (15)Current frame: Child-SP         RetAddr          Caller, Callee0000005c65fff030 00007ffc5988b78b (MethodDesc 00007ffc594b9090 +0xb System.Threading.Thread.Sleep(Int32))0000005c65fff060 00007ffbfc3c946b (MethodDesc 00007ffbfc45eb10 +0x2b Tccc.WindbgDemoAPP.MainWindow+<>c.<sleepBtn_Click>b__22_0(System.Object))0000005c65fff090 00007ffc59853480 (MethodDesc 00007ffc592f8a18 +0x170 System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean))0000005c65fff160 00007ffc59853305 (MethodDesc 00007ffc594c5248 +0x15 System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean))0000005c65fff190 00007ffc5987a506 (MethodDesc 00007ffc594e3570 +0x76 System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem())0000005c65fff1d0 00007ffc59879746 (MethodDesc 00007ffc5965fbc0 +0x156 System.Threading.ThreadPoolWorkQueue.Dispatch())
    • RetAddr列代表当前方法的代码地址入口，同上的IP列。Caller, Callee列包含方法MethodDesc值和方法签名信息。
  3. eestack命令
    • 作用：查看所有线程的堆栈，完全等价于每个线程执行dumpstack命令
    • EEStack [-short] [-EE]
      • -EE同上
      • -short：只输出符合条件的线程堆栈：持有锁的线程、GC挂起的线程、正在执行托管代码的线程。
    • 输出示例和解读：同上，略。
  4. dso命令
    • 作用：查看当前线程的全部托管对象。
    • DSO [-verify] [top stack [bottom stack]]
    • 输出示例和解读：
    • 0:015> !dso OS Thread Id: 0x759c (15)RSP/REG          Object           Name0000005C65FFEF58 0000023f43200628 System.Threading.QueueUserWorkItemCallback0000005C65FFEF78 0000023f43200690 System.Threading.ExecutionContext0000005C65FFEF80 0000023f43200650 System.Threading.ContextCallback0000005C65FFEF98 0000023f43200650 System.Threading.ContextCallback0000005C65FFEFC0 0000023f43201fe8 System.Threading.Thread0000005C65FFF000 0000023f43200690 System.Threading.ExecutionContext0000005C65FFF020 0000023f43201fe8 System.Threading.Thread0000005C65FFF028 0000023f43200628 System.Threading.QueueUserWorkItemCallback0000005C65FFF048 0000023f43200650 System.Threading.ContextCallback0000005C65FFF050 0000023f43200690 System.Threading.ExecutionContext0000005C65FFF060 0000023f43200690 System.Threading.ExecutionContext0000005C65FFF088 0000023f43200628 System.Threading.QueueUserWorkItemCallback0000005C65FFF0A0 0000023f431ffd68 Tccc.WindbgDemoAPP.MainWindow+<>c0000005C65FFF0E0 0000023f43201fe8 System.Threading.Thread0000005C65FFF140 0000023f43200628 System.Threading.QueueUserWorkItemCallback0000005C65FFF148 0000023f43200690 System.Threading.ExecutionContext0000005C65FFF1E0 0000023f43200628 System.Threading.QueueUserWorkItemCallback0000005C65FFF228 0000023f43201cb0 System.Threading.ThreadPoolWorkQueueThreadLocals0000005C65FFF230 0000023f431ffdc0 System.Threading.ThreadPoolWorkQueue0000005C65FFF250 0000023f43200628 System.Threading.QueueUserWorkItemCallback
    • Object列是对象地址，Name列时对象类型名称。

查看锁的命令

  1. syncblk命令
    • 作用：查看进程中同步块锁的持有情况和等待情况。常用于分析死锁问题。
    • SyncBlk [-all | <syncblk number>]
      • 默认输出被线程持有的锁信息
      • -all：输出全部的SyncBlock对象信息
      • syncblk number：指定锁编号
    • 输出示例和解读：
    • 0:098> !syncblkIndex SyncBlock MonitorHeld Recursion Owning Thread Info  SyncBlock Owner  510 000002bb0513d4a8           79         1 000002bb073568c0 f9e8 177   000002be7520adb0 System.Object  530 000002bb0513a1f8          219         1 000002bb06a17770 26bdc 112   000002bd74f07d30 System.Object  567 000002bb0513e148            5         1 000002bb06ce6f40 24ce0 113   000002be74f320b8 System.Object 1343 000002bb0513c2b8            7         1 000002bb06a17770 26bdc 112   000002bd7515b158 ServiceStack.Redis.RedisSentinelWorker-----------------------------Total           1369CCW             3RCW             2ComClassFactory 0Free            507
    • Index列是编号，SyncBlock列是锁地址，MonitorHeld是等待计数器，Recursion代表持有此锁的线程数量，Owning Thread Info这3列代表持有锁的线程信息，SyncBlock Owner代表锁对象地址和类型。
    • MonitorHeld值的含义：当一个线程持有了锁的时候 MonitorHeld+1 ，当一个线程在等待锁的时候 MonitorHeld+2。因此示例中510号锁的等待线程数量=(79-1)/2=39。

查看进程信息、内存分布的命令

  1. EEVersion命令
    • 作用：查看CLR版本信息
    • 输出示例和解读：
    • 0:001> !eeversion4.8.4380.0 freeServer mode with 8 gc heapsSOS Version: 4.8.4380.0 retail build
  2. DumpDomain命令
    • 作用：查看应用程序域信息
    • DumpDomain [<domain address>]，参数为指定程序域的地址，不带参数输出全部程序域信息。
    • 输出示例和解读：
    • 查看代码
      0:015> !dumpdomain--------------------------------------System Domain:      00007ffc5c3006e0LowFrequencyHeap:   00007ffc5c300c58HighFrequencyHeap:  00007ffc5c300ce8StubHeap:           00007ffc5c300d78Stage:              OPENName:               None--------------------------------------Shared Domain:      00007ffc5c300110LowFrequencyHeap:   00007ffc5c300c58HighFrequencyHeap:  00007ffc5c300ce8StubHeap:           00007ffc5c300d78Stage:              OPENName:               NoneAssembly:           0000024cdf62db80 [C:\WINDOWS\Microsoft.Net\assembly\GAC_64\mscorlib\v4.0_4.0.0.0__b77a5c561934e089\mscorlib.dll]ClassLoader:        0000024cdf62dca0  Module Name00007ffc592f1000            C:\WINDOWS\Microsoft.Net\assembly\GAC_64\mscorlib\v4.0_4.0.0.0__b77a5c561934e089\mscorlib.dll--------------------------------------Domain 1:           0000024cdf5c4cf0LowFrequencyHeap:   0000024cdf5c54e8HighFrequencyHeap:  0000024cdf5c5578StubHeap:           0000024cdf5c5608Stage:              OPENSecurityDescriptor: 0000024cdf5c7300Name:               Tccc.WindbgDemoAPP.exeAssembly:           0000024cdf62db80 [C:\WINDOWS\Microsoft.Net\assembly\GAC_64\mscorlib\v4.0_4.0.0.0__b77a5c561934e089\mscorlib.dll]ClassLoader:        0000024cdf62dca0SecurityDescriptor: 0000024cdf6317c0  Module Name00007ffc592f1000            C:\WINDOWS\Microsoft.Net\assembly\GAC_64\mscorlib\v4.0_4.0.0.0__b77a5c561934e089\mscorlib.dllAssembly:           0000024cdf640bb0 [D:\50LearningSln\Tccc\Tccc.WindbgDemoAPP\bin\x64\Debug\Tccc.WindbgDemoAPP.exe]ClassLoader:        0000024cdf640cd0SecurityDescriptor: 0000024cdf640ac0  Module Name00007ffbfc2a4140            D:\50LearningSln\Tccc\Tccc.WindbgDemoAPP\bin\x64\Debug\Tccc.WindbgDemoAPP.exe
    • 输出内容包含系统程序域、共享程序域、Domain1等。同时，程序域中加载的程序集信息也打印出来。这里的程序集路径可以准确判断程序加载的文件位置，非常有用。
  3.  eeheap命令
    • 作用：查看进程内的CLR内存分布。
    • EEHeap [-gc] [-loader]，默认输出全部内存分布信息。
      • -gc只输出gc堆和大对象堆
      • -loader只输出加载器相关的内存分布
    • 输出示例和解读：
    • 查看代码
      0:015> !eeheapLoader Heap:--------------------------------------System Domain:     00007ffc5c3006e0LowFrequencyHeap:  00007ffbfc290000(3000:3000) Size: 0x3000 (12288) bytes.HighFrequencyHeap: 00007ffbfc294000(9000:3000) Size: 0x3000 (12288) bytes.StubHeap:          00007ffbfc29d000(3000:3000) 00007ffbfc450000(10000:1000) Size: 0x4000 (16384) bytes.Virtual Call Stub Heap:  IndcellHeap:     00007ffbfc340000(6000:1000) Size: 0x1000 (4096) bytes.  LookupHeap:      00007ffbfc34c000(4000:1000) Size: 0x1000 (4096) bytes.  ResolveHeap:     00007ffbfc376000(3a000:2000) Size: 0x2000 (8192) bytes.  DispatchHeap:    00007ffbfc350000(26000:1000) Size: 0x1000 (4096) bytes.  CacheEntryHeap:  00007ffbfc346000(6000:1000) Size: 0x1000 (4096) bytes.Total size:        Size: 0x10000 (65536) bytes.--------------------------------------Shared Domain:     00007ffc5c300110LowFrequencyHeap:  00007ffbfc290000(3000:3000) Size: 0x3000 (12288) bytes.HighFrequencyHeap: 00007ffbfc294000(9000:3000) Size: 0x3000 (12288) bytes.StubHeap:          00007ffbfc29d000(3000:3000) 00007ffbfc450000(10000:1000) Size: 0x4000 (16384) bytes.Virtual Call Stub Heap:  IndcellHeap:     00007ffbfc340000(6000:1000) Size: 0x1000 (4096) bytes.  LookupHeap:      00007ffbfc34c000(4000:1000) Size: 0x1000 (4096) bytes.  ResolveHeap:     00007ffbfc376000(3a000:2000) Size: 0x2000 (8192) bytes.  DispatchHeap:    00007ffbfc350000(26000:1000) Size: 0x1000 (4096) bytes.  CacheEntryHeap:  00007ffbfc346000(6000:1000) Size: 0x1000 (4096) bytes.Total size:        Size: 0x10000 (65536) bytes.--------------------------------------Domain 1:          0000024cdf5c4cf0LowFrequencyHeap:  00007ffbfc2a0000(3000:3000) 00007ffbfc430000(10000:d000) Size: 0x10000 (65536) bytes.HighFrequencyHeap: 00007ffbfc2a3000(a000:9000) 00007ffbfc440000(10000:f000) Size: 0x18000 (98304) bytes total, 0x1000 (4096) bytes wasted.StubHeap:          00007ffbfc2ad000(3000:1000) Size: 0x1000 (4096) bytes.Virtual Call Stub Heap:  IndcellHeap:     00007ffbfc2b0000(4000:1000) Size: 0x1000 (4096) bytes.  LookupHeap:      00007ffbfc2bb000(2000:1000) Size: 0x1000 (4096) bytes.  ResolveHeap:     00007ffbfc2ec000(54000:8000) Size: 0x8000 (32768) bytes.  DispatchHeap:    00007ffbfc2bd000(2f000:3000) Size: 0x3000 (12288) bytes.  CacheEntryHeap:  00007ffbfc2b4000(7000:1000) Size: 0x1000 (4096) bytes.Total size:        Size: 0x37000 (225280) bytes total, 0x1000 (4096) bytes wasted.--------------------------------------Jit code heap:LoaderCodeHeap:    0000000000000000(0:0) Size: 0x0 (0) bytes.Total size:        Size: 0x0 (0) bytes.--------------------------------------Module Thunk heaps:Module 00007ffc592f1000: Size: 0x0 (0) bytes.Module 00007ffbfc2a4140: Size: 0x0 (0) bytes.Module 00007ffc192a1000: Size: 0x0 (0) bytes.Module 00007ffc1aa31000: Size: 0x0 (0) bytes.Module 00007ffc54e51000: Size: 0x0 (0) bytes.Module 00007ffc18d91000: Size: 0x0 (0) bytes.Module 00007ffc4e2d1000: Size: 0x0 (0) bytes.Module 00007ffc36e51000: Size: 0x0 (0) bytes.Module 00007ffc4c0d1000: Size: 0x0 (0) bytes.Module 00007ffc4b821000: Size: 0x0 (0) bytes.Module 00007ffc17241000: Size: 0x0 (0) bytes.Module 00007ffbfc44bce8: Size: 0x0 (0) bytes.Module 00007ffbfc44c6a8: Size: 0x0 (0) bytes.Module 00007ffbfc44d2b8: Size: 0x0 (0) bytes.Module 00007ffc13541000: Size: 0x0 (0) bytes.Module 00007ffc22ef1000: Size: 0x0 (0) bytes.Total size:              Size: 0x0 (0) bytes.--------------------------------------Module Lookup Table heaps:Module 00007ffc592f1000: Size: 0x0 (0) bytes.Module 00007ffbfc2a4140: Size: 0x0 (0) bytes.Module 00007ffc192a1000: Size: 0x0 (0) bytes.Module 00007ffc1aa31000: Size: 0x0 (0) bytes.Module 00007ffc54e51000: Size: 0x0 (0) bytes.Module 00007ffc18d91000: Size: 0x0 (0) bytes.Module 00007ffc4e2d1000: Size: 0x0 (0) bytes.Module 00007ffc36e51000: Size: 0x0 (0) bytes.Module 00007ffc4c0d1000: Size: 0x0 (0) bytes.Module 00007ffc4b821000: Size: 0x0 (0) bytes.Module 00007ffc17241000: Size: 0x0 (0) bytes.Module 00007ffbfc44bce8: Size: 0x0 (0) bytes.Module 00007ffbfc44c6a8: Size: 0x0 (0) bytes.Module 00007ffbfc44d2b8: Size: 0x0 (0) bytes.Module 00007ffc13541000: Size: 0x0 (0) bytes.Module 00007ffc22ef1000: Size: 0x0 (0) bytes.Total size:              Size: 0x0 (0) bytes.--------------------------------------Total LoaderHeap size:   Size: 0x57000 (356352) bytes total, 0x1000 (4096) bytes wasted.=======================================Number of GC Heaps: 1generation 0 starts at 0x0000024ce1407c30generation 1 starts at 0x0000024ce12a1018generation 2 starts at 0x0000024ce12a1000ephemeral segment allocation context: none         segment             begin         allocated              size0000024ce12a0000  0000024ce12a1000  0000024ce14edc48  0x24cc48(2411592)Large object heap starts at 0x0000024cf12a1000         segment             begin         allocated              size0000024cf12a0000  0000024cf12a1000  0000024cf12c31f0  0x221f0(139760)Total Size:              Size: 0x26ee38 (2551352) bytes.------------------------------GC Heap Size:            Size: 0x26ee38 (2551352) bytes.
    • 输出内容包含各个程序域内存信息、JIT堆、GC堆、加载器堆等地址信息。
  4. dumpheap命令
    • 作用：查看内存中的对象信息，非常有用。
    • DumpHeap [-stat]  [-mt <MethodTable address>] [-type <partial type name>]
      • 默认输出全部的对象明细，数据量大，一般都会带参数限制输出大小。
      • -stat：按照对象的类型，汇总输出，最常用的选项。
      • -mt <MethodTable address>：根据MethodTable地址过滤对象。
      • -type <partial type name>：根据类型名称过滤对象，区分大小写，不需要提供完整类型。
    • 输出示例和解读：
    • 0:001> !dumpheap -stat -mt 00007ffbee0abd78Statistics:              MT    Count    TotalSize Class Name00007ffbee0abd78    34150      1366000 System.Net.SocketAddressTotal 34150 objects0:001> !dumpheap -stat -type Net.SocketAddressStatistics:              MT    Count    TotalSize Class Name00007ffbee0abd78    34150      1366000 System.Net.SocketAddressTotal 34150 objects
  5. dumpobj命令
    • 作用：查看对象信息
    • DumpObj <object address>
    • 输出示例和解读：
    • 查看代码
      0:015> !DumpObj /d 0000024ce12acc98Name:        System.Threading.ThreadMethodTable: 00007ffc59304e08EEClass:     00007ffc59481748Size:        96(0x60) bytesFile:        C:\WINDOWS\Microsoft.Net\assembly\GAC_64\mscorlib\v4.0_4.0.0.0__b77a5c561934e089\mscorlib.dllFields:              MT    Field   Offset                 Type VT     Attr            Value Name00007ffc5938ea98  400192d        8 ....Contexts.Context  0 instance 0000000000000000 m_Context00007ffc5930c3a0  400192e       10 ....ExecutionContext  0 instance 0000024ce12d30a0 m_ExecutionContext00007ffc59303db8  400192f       18        System.String  0 instance 0000000000000000 m_Name00007ffc59306628  4001930       20      System.Delegate  0 instance 0000000000000000 m_Delegate00007ffc59308090  4001931       28 ...ation.CultureInfo  0 instance 0000000000000000 m_CurrentCulture00007ffc59308090  4001932       30 ...ation.CultureInfo  0 instance 0000000000000000 m_CurrentUICulture00007ffc593041d0  4001933       38        System.Object  0 instance 0000000000000000 m_ThreadStartArg00007ffc5930d260  4001934       40        System.IntPtr  1 instance      24cdf5efd80 DONT_USE_InternalThread00007ffc59306ad8  4001935       48         System.Int32  1 instance                2 m_Priority00007ffc59306ad8  4001936       4c         System.Int32  1 instance                1 m_ManagedThreadId00007ffc5930a420  4001937       50       System.Boolean  1 instance                0 m_ExecutionContextBelongsToOuterScope00007ffc59326f88  4001938      e30 ...LocalDataStoreMgr  0   shared           static s_LocalDataStoreMgr                                 >> Domain:Value  0000024cdf5c4cf0:NotInit  <<00007ffc5a588408  400193a      e38 ...eInfo, mscorlib]]  0   shared           static s_asyncLocalCurrentCulture                                 >> Domain:Value  0000024cdf5c4cf0:NotInit  <<00007ffc5a588408  400193b      e40 ...eInfo, mscorlib]]  0   shared           static s_asyncLocalCurrentUICulture                                 >> Domain:Value  0000024cdf5c4cf0:NotInit  <<00007ffc59328a18  4001939       18 ...alDataStoreHolder  0   shared         TLstatic s_LocalDataStore    >> Thread:Value <<00007ffc59306ad8  400193c      d10         System.Int32  1   shared         TLstatic t_currentProcessorIdCache    >> Thread:Value <<
    • 其中Attr列的instance代表当前行是实例字段，Value是Field的值，Name是当前Field的名称。

查看异常的命令

  1. pe命令
    • 作用：查看当前线程的异常。
    • 输出示例和解读：
    • 查看代码
      0:098> !peException object: 000002bbf5127940Exception type:   ServiceStack.Redis.RedisExceptionMessage:          Host:10.201.107.xxx,Port:26379 Exceeded timeout of 00:00:03InnerException:   System.Net.Sockets.SocketException, Use !PrintException 000002bef5278f08 to see more.StackTrace (generated):    SP               IP               Function    000000D8D77FC260 00007FFB92F54063 UNKNOWN!ServiceStack.Redis.RedisNativeClient.SendReceive[[System.__Canon, mscorlib]](Byte[][], System.Func`1<System.__Canon>, System.Action`1<System.Func`1<System.__Canon>>, Boolean)+0x2b3    000000D8D77FE510 00007FFB92F596C4 UNKNOWN!ServiceStack.Redis.RedisNativeClient.SendExpectMultiData(Byte[][])+0xd4...省略....    000000D8D77FE8A0 00007FFB92F5D681 UNKNOWN!ServiceStack.Redis.RedisSubscription.SubscribeToChannelsMatching(System.String[])+0x51    000000D8D77FE8D0 00007FFB92F5CFC5 UNKNOWN!ServiceStack.Redis.RedisPubSubServer.RunLoop()+0x1d5StackTraceString: <none>HResult: 80131500
    • 输出内容包含了完整的异常信息，比如异常对象地址、Message内容、异常堆栈，甚至连InnerException也有提示。

总结

本文不仅是教程，也是一份手册。SOS提供了非常多的命令，需要逐步摸索实践，这些命令只有亲自实践后才能够真正掌握。

参考资料

SOS.dll (SOS Debugging Extension) - .NET Framework | Microsoft Docs

posted @ 2022-02-22 21:57 志存高远，脚踏实地 阅读(10) 评论(0) 编辑 收藏 举报
上一篇：图解python|for循环
下一篇：AzureKeyVault（三）通过Microsoft.Azure.KeyVault类库在.NETCore上获取Secrets
回帖
    张三

    张三 （王者 段位）

    821 积分 (2)粉丝 (41)源码

     

    温馨提示

    亦奇源码

    最新会员