minidump 분석

Visual studio 이상의 정보를 얻기

!chkimg

Whether they were caused by bad RAM, bad disk, or a passing cosmic ray, I don’t know, but I was able to conclude that this bug didn’t need to be investigated further

https://mcc.id.au/blog/2018/07/memory-corruption

기타 여러 명령어

http://www.debuginfo.com/articles/easywindbg2.html

메모리 관련, fulldump 에서 쓸만한 정보를 보여주는 듯

!address -summary
!address
!vadump

minidump에서는 별로 효과적이지 못함

0:000> !address -summary
The current target does not provide full memory information. No meaningful summary available.
Use !address with no arguments to display the available virtual memory map of the target.
0:000> !address 0x6000000

Usage:                  <unknown>
Base Address:           04730000
End Address:            0e5afa20
Region Size:            09e7fa20 ( 158.499 MB)
State:                  <info not present at the target>
Protect:                <info not present at the target>
Type:                   <info not present at the target>
Allocation Base:        <info not present at the target>
Allocation Protect:     <info not present at the target>

local frame 출력

!for_each_frame dv /t
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
00 006afe88 0043096e CrashDemo!TestFunc+0x2e [c:\tests\crashdemo\crashdemo.cpp @ 124]
int * pParam = 0x00000000
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
01 006aff6c 00430f31 CrashDemo!WorkerThread+0x5e [c:\tests\crashdemo\crashdemo.cpp @ 115]
void * lpParam = 0x00000000
int * TempPtr = 0x00000000
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
02 006affa8 00430ea2 CrashDemo!_callthreadstartex+0x51 
  [f:\rtm\vctools\crt_bld\self_x86\crt\src\threadex.c @ 348]
struct _tiddata * ptd = 0x00355188
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

(And of course, we have to remember that in optimized builds some local variables can be optimized away, enregistered, or reused to store other data throughout the lifetime of the function, and as a result the values reported by 'dv' command can be incorrect)

exception 추적

~*kb