Errata for Memory Dump Analysis Anthology, Volume 5

First printing

--- Page 8

--- Page 99

Type:
    Misprint
Original text:
    Distrubuted Spike
Reported by:
    Author
BugFix:
    Distributed Spike

--- Page 9

--- Page 133

Type:
    Misprint
Original text:
    Tthread
Reported by:
    Author
BugFix:
    Thread

--- Page 284

Type:
    Misprint
Original text:
    Statement current Jmi > Jmj, i < j < N
Reported by:
    Author
BugFix:
    Statement current Jmi < Jmj, i < j < N

--- Page 289

Type:
    Misprint
Original text:
    Of cource, this process is iterative and parts of what once was foreground become background and candidate for further filtering:
Reported by:
    Author
BugFix:
    Of course, this process is iterative and parts of what once was foreground become background and candidates for further filtering:

--- Page 290

Type:
    Grammar
Original text:
    In this pattern from software narratology (Volume 3, page 342) see sudden unfamiliar trace statements
Reported by:
    Author
BugFix:
    In this pattern from software narratology (Volume 3, page 342) we see sudden unfamiliar trace statements

--- Page 291

Type:
    Misprint
Original text:
    Example of a familar trace:
Reported by:
    Author
BugFix:
    Example of a familiar trace:

--- Page 296

Type:
    Misprint
Original text:
    By looking at Thread of Activity (Volume 4, page 339) we can sometimes also infer the possible component name based on surrounding trace messages with present TMF files, escpecially when we have source code access.
Reported by:
    Author
BugFix:
    By looking at Thread of Activity (Volume 4, page 339) we can sometimes also infer the possible component name based on surrounding trace messages with present TMF files, especially when we have source code access.