记一次 .NET 某医疗器械 程序崩溃分析

一:背景1.讲故事前段时间有位朋友在微信上找到我,说他的程序偶发性崩溃,让我帮忙看下怎么回事,上面给的压力比较大,对于这种偶发性崩溃,比较好的办法就是利用 AEDebug 在程序崩溃的时候自动抽一管血出来,看看崩溃点是什么,其实我的系列文章中,关于崩溃类的dump比较少,刚好补一篇上来,话不多说 , 上 windbg。
二:WinDbg 分析1. 崩溃点在哪里在 windbg 中有一个 !analyze -v 命令可以自动化分析,输出信息如下:
0:120> !analyze -v**********************************************************************************Exception Analysis**********************************************************************************CONTEXT:(.ecxr)rax=00000000032fed38 rbx=00000000c0000374 rcx=0000000000000000rdx=0000000000000020 rsi=0000000000000001 rdi=00007ffbada727f0rip=00007ffbada0a8f9 rsp=000000003103c8b0 rbp=0000000000c40000 r8=00007ffb779bdab7r9=00007ffb782e94c0 r10=0000000000002000r11=000000002c4aa498 r12=0000000000000000 r13=000000003103eb60r14=0000000000000000 r15=000000002c873720iopl=0nv up ei pl nz na pe nccs=0033ss=002bds=002bes=002bfs=0053gs=002befl=00000202ntdll!RtlReportFatalFailure+0x9:00007ffb`ada0a8f9 eb00jmpntdll!RtlReportFatalFailure+0xb (00007ffb`ada0a8fb)Resetting default scopeEXCEPTION_RECORD:(.exr -1)ExceptionAddress: 00007ffbada0a8f9 (ntdll!RtlReportFatalFailure+0x0000000000000009)ExceptionCode: c0000374ExceptionFlags: 00000001NumberParameters: 1Parameter[0]: 00007ffbada727f0...从卦中的 ExceptionCode: c0000374 异常码来看,表示当前 nt堆损坏,这就尴尬了,一个C#程序咋会把 windows nt 堆给弄坏了 , 可能是引入了第三方的 C++ 代码 。
由于异常分异常前和异常后,所以需要用 .ecxr 将当前线程切到异常前的崩溃点 , 然后使用 k 观察当前的线程栈 。
0:120> .ecxr ; krax=00000000032fed38 rbx=00000000c0000374 rcx=0000000000000000rdx=0000000000000020 rsi=0000000000000001 rdi=00007ffbada727f0rip=00007ffbada0a8f9 rsp=000000003103c8b0 rbp=0000000000c40000 r8=00007ffb779bdab7r9=00007ffb782e94c0 r10=0000000000002000r11=000000002c4aa498 r12=0000000000000000 r13=000000003103eb60r14=0000000000000000 r15=000000002c873720iopl=0nv up ei pl nz na pe nccs=0033ss=002bds=002bes=002bfs=0053gs=002befl=00000202ntdll!RtlReportFatalFailure+0x9:00007ffb`ada0a8f9 eb00jmpntdll!RtlReportFatalFailure+0xb (00007ffb`ada0a8fb)*** Stack trace for last set context - .thread/.cxr resets it # Child-SPRetAddrCall Site00 00000000`3103c8b0 00007ffb`ada0a8c3ntdll!RtlReportFatalFailure+0x901 00000000`3103c900 00007ffb`ada1314entdll!RtlReportCriticalFailure+0x9702 00000000`3103c9f0 00007ffb`ada1345antdll!RtlpHeapHandleError+0x1203 00000000`3103ca20 00007ffb`ad9aef41ntdll!RtlpHpHeapHandleError+0x7a04 00000000`3103ca50 00007ffb`ad9be520ntdll!RtlpLogHeapFailure+0x4505 00000000`3103ca80 00007ffb`aa3882bfntdll!RtlFreeHeap+0x966e006 00000000`3103cb20 00007ffb`66fac78fKERNELBASE!LocalFree+0x2f07 00000000`3103cb60 00007ffb`66f273a4mscorlib_ni+0x63c78f08 00000000`3103cc10 00007ffb`185c4fdemscorlib_ni!System.Runtime.InteropServices.Marshal.FreeHGlobal+0x24 [f:\dd\ndp\clr\src\BCL\system\runtime\interopservices\marshal.cs @ 1212]09 00000000`3103cc50 00007ffb`185c4fa10x00007ffb`185c4fde0a 00000000`3103cca0 00007ffb`185edc820x00007ffb`185c4fa1...从卦中的 KERNELBASE!LocalFree 方法可知,程序正在释放一个 堆块,在释放的过程中抛出了异常,那为什么会释放失败呢? 原因就比较多了,比如:

  • 原因1:Free 一个已 Free 的堆块
  • 原因2:Free 了一个别人的堆块
那到底是哪一种情况呢? 有经验的朋友应该知道,ntheap 默认开启了 损坏退出 机制,用 !heap -s 命令就能显示出这种损坏原因 。
0:120> !heap -s************************************************************************************************************************NT HEAP STATS BELOW*****************************************************************************************************************************************************************************************HEAP ERROR DETECTED*****************************************************************Details:Heap address:0000000000c40000Error address: 000000002c873710Error type: HEAP_FAILURE_BLOCK_NOT_BUSYDetails:The caller performed an operation (such as a freeor a size check) that is illegal on a free block.Follow-up:Check the error's stack trace to find the culprit.Stack trace:Stack trace at 0x00007ffbada7284800007ffbad9aef41: ntdll!RtlpLogHeapFailure+0x4500007ffbad9be520: ntdll!RtlFreeHeap+0x966e000007ffbaa3882bf: KERNELBASE!LocalFree+0x2f00007ffb66fac78f: mscorlib_ni+0x63c78f00007ffb66f273a4: mscorlib_ni!System.Runtime.InteropServices.Marshal.FreeHGlobal+0x2400007ffb185c4fde: +0x185c4fdeLFH Key: 0x1d4fd2a71d8b8280Termination on corruption : ENABLEDHeapFlagsReservCommitVirtFreeListUCRVirtLockFast(k)(k)(k)(k) lengthblocks cont. heap-------------------------------------------------------------------------------------0000000000c40000 00000002167561368816364220140520LFH...

推荐阅读