Errata for Memory Dump Analysis Anthology, Volume 4

First printing

--- Page 336

Type:
    Misprint
Original text:
    To avoid being lost in this discusssion I repeat main results:
Reported by:
    Author
BugFix:
    To avoid being lost in this discussion I repeat main results:

--- Page 340

Type:
    Misprint
Original text:
    Ususally when we see an error indication we select its current thread of activity and investigate what happened in this process and thread before.
Reported by:
    Author
BugFix:
    Usually when we see an error indication we select its current thread of activity and investigate what happened in this process and thread before.

--- Page 342

Type:
    Misprint
Original text:
    We can find an example from Discontinuity (page 341) pattern where the possibility of a sudden and silent gap in trace statements could happen because not all necessary componets were selected for tracing.
Reported by:
    Author
BugFix:
    We can find an example from Discontinuity (page 341) pattern where the possibility of a sudden and silent gap in trace statements could happen because not all necessary components were selected for tracing.

--- Page 346

Type:
    Grammar
Original text:
    if a viewer support zooming
Reported by:
    Author
BugFix:
    if a viewer supports zooming

--- Page 350

Type:
    Misprint
Original text:
    When we run the application in terminal services envirinment all windows (including other processes) are shown with an incorrect dimension.
Reported by:
    Author
BugFix:
    When we run the application in terminal services environment all windows (including other processes) are shown with an incorrect dimension.

--- Page 351

Type:
    Misprint
Original text:
    addition WindowHistory trace to see how corrdinates of all windows are changed over time.
Reported by:
    Author
BugFix:
    addition WindowHistory trace to see how coordinates of all windows are changed over time.