Errata for Memory Dump Analysis Anthology, Volume 2

First printing

--- Page 63

Type:
    Reference
Original text:
    - Insufficient Memory (virtual memory, page Error! Bookmark not defined.)
Reported by:
    author
BugFix:
    - Insufficient Memory (virtual memory, page 210)

--- Page 166

Type:
    Reference
Original text:
    Suspended Thread pattern, page Error! Bookmark not defined.
Reported by:
    author
BugFix:
    Suspended Thread pattern, page 161

--- Page 223

Type:
    Reference
Original text:
    Wild Code, page Error! Bookmark not defined.
Reported by:
    author
BugFix:
    Wild Code, page 219

--- Page 300

Type:
    Reference
Original text:
    Code Path Locality (similar partial stack traces and code residues, page Error! Bookmark not defined.)
Reported by:
    author
BugFix:
    Code Path Locality (similar partial stack traces and code residues, page 239)

--- Pages 12, 360, 361, 460, 470

Type:
    Spelling
Original text:
    Colometric Computer Memory Dating
Reported by:
    author
BugFix:
    Colorimetric Computer Memory Dating

--- Page 294

Type:
    Misprint
Original text:
    Usually his happens when the DLL is loaded from different locations.
Reported by:
    SungHyun Kim
BugFix:
    Usually this happens when the DLL is loaded from different locations.

--- Page 319

Type:
    Miscalculation
Original text:
    It could be the case that the thread in question was waiting 98.9% of the time, then did some computation for 0.01% and was waiting again 1% of the time or it could be the case that it was doing computation 0.01% of the time initially and then waiting the rest of the time (99.9%) until the dump was saved.
Reported by:
    SungHyun Kim
BugFix:
    It could be the case that the thread in question was waiting 98.9% of the time, then did some computation for 0.1% and was waiting again 1% of the time or it could be the case that it was doing computation 0.1% of the time initially and then waiting the rest of the time (99.9%) until the dump was saved.