Index_I


I

IdiomTable

class, 317, 333

object, 316, 317, 320

IEEE94, 2

If-then-else, 81, 325

Inadequate data, 410–11

Inattention failures, 394–99

interrupt sequence, omit step, 395–96

interrupt sequence, repeat step, 396

interrupt sequence, start another sequence, 394–95

multiple matches, incorrect choice, 397

multiple sequences active, steps mixed, 397–98

sensory input interferes with active

sequence, 398–99

sequence interrupted, loss of control, 396–97

See also Error causes

Indentation, 181

Indent utility, 329

Inductive-analysis strategy, 196–97

assumptions, 196–97

choosing, 199

control structure, 197

defined, 196

See also Debugging strategies

Information technology (IT), 20

Information availability, 408

Initialization errors, 371–72

Input

requirement reduction, 207–8

sets, unacceptable performance and, 212

Insert function, 80, 81, 84, 85

identification printing, 151

problems coming out of, 98

sequence, 98

testing, 100–111

value trace, 151

Insure++, 489–93

analysis comparison, 504, 505

Chaperon mode, 490

defined, 489

dynamic-memory errors, 491

features, 489–90

invalid pointer variable uses, 492

memory-leak problem detection, 489

memory leak errors, 492–93

pointer-reference problem detection, 489

Source Code Instrumentation mode, 490–91

technology, 490–93

usage, 493

See also Dynamic-analysis tools

Integrated development environments (IDEs), 56, 57

Intellectual disciplines, 2–4

way of the computer scientist, 4

way of the detective, 3

way of the engineer, 3–4

way of the mathematician, 3

way of the psychologist, 3

way of the safety expert, 3

Interacting, debugging by, 11

Interprocedural analysis, 195

Intraprocedural analysis, 195

Invalid expressions, 378–79

Investigations

bug 1 (case study I), 79–82

bug 1 (case study II), 263–64

bug 1 (case study III), 305–6

bug 2 (case study I), 83–88

bug 2 (case study II), 266

bug 2 (case study III), 309–10

bug 3 (case study I), 92–93

bug 3 (case study II), 267

bug 3 (case study III), 312–15

bug 4 (case study I), 95–99

bug 4 (case study II), 268

bug 4 (case study III), 316–17

bug 5 (case study I), 112–13

bug 5 (case study III), 318

bug 6 (case study I), 115–16

bug 6 (case study III), 320–21

bug 7 (case study I), 118–20

bug 7 (case study III), 323–25

bug 8 (case study I), 124–25

bug 8 (case study III), 327

bug 9 (case study I), 128–32

bug 9 (case study III), 329–30

bug 10 (case study I), 134–35

bug 10 (case study III), 333

bug 11 (case study I), 138–39

bug 12 (case study I), 144–45

bug 13 (case study I), 151–52

bug 15 (case study I), 157–58




Debugging by Thinking. A Multidisciplinary Approach
Debugging by Thinking: A Multidisciplinary Approach (HP Technologies)
ISBN: 1555583075
EAN: 2147483647
Year: 2002
Pages: 172

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net