After looking at one dump today where all thread environment blocks were zeroed, import table corrupt and recalling some similar cases Iencountered previously I came up with the next pattern: Lateral Damage.
Whenthis problem happens you don’t have much choice and your first temptation is to apply Alien Component anti-patternunless your module listiscorrupt andyou have manifestation of anothercommon problemIwill talk about next time: Corrupt Dump.
Anti-pattern isnot always bad solution ifcomplemented by subsequent verification and backed by experience.If yougetdamagedprocess and thread structuresyou canpoint toa suspiciouscomponent (supported by some evidence like raw stack analysis and educated guess) and request additional dumps in hope to get less damaged process space or seethat component again. At the very end if removing it stabilizes the customer environment it proves you were right.
- Dmitry Vostokov -
'Crash dump 불펌스페샬' 카테고리의 다른 글
| Crash Dump Analysis Patterns (Part 6) (0) | 2007.05.13 |
|---|---|
| Crash Dump Analysis Patterns (Part 7) (2) | 2007.05.13 |
| Crash Dump Analysis Patterns (Part 5) (1) | 2007.05.13 |
| Crash Dump Analysis Patterns (Part 3) (2) | 2007.05.13 |
| Crash Dump Analysis Patterns (Part 2) (1) | 2007.05.13 |
