Joy of Debugging, The
Joy of Debugging, The
Cantrill, Bryan; Pacheco, David
Pearson Education (US)
04/2025
500
Mole
Inglês
9780134578729
Pré-lançamento - envio 15 a 20 dias após a sua edição
Descrição não disponível.
Draft table of contents
Part 1: Foundations
* Introduction (embracing debugging as both a first-class part of our jobs as engineers, and as an enjoyable, rewarding part of the craft of software engineering)
* How software fails: taxonomy of failure (implicit and explicit, fatal and non-fatal)
* Understanding software failure: the scientific method (including the roles of reproducibility, for testing hypotheses and gathering data)
Part 2: Approaches
* In situ debugging
-- Using Dynamic Tracing --Logging
-- Basic tools (e.g., finding information about what processes are doing?)
* Postmortem debugging (fatal failure)
Part 3: Specific expertise
These chapters start with narrative prose describing basic concepts, and then enumerate tips and techniques related to the problem space.
* Debugging memory issues in native code (corruption, use-after-free)
* Debugging resource exhaustion in native code
* Debugging multi-threaded programs
* Debugging in dynamic environments (including GC-related issues)
* Debugging the network (including TCP issues, jumbo frames, partitions)
* Debugging distributed systems
* Debugging performance issues
* Debugging psychotic issues
Part 4: Advanced topics
* Debugging-driven development (embracing debugging at development-time)
* What to do when you're stuck
* Debugging unfamiliar systems
* Debugging during an outage
* Building an organization for debugging
* Describing failure [rigorously, and the importance of it]
Part 1: Foundations
* Introduction (embracing debugging as both a first-class part of our jobs as engineers, and as an enjoyable, rewarding part of the craft of software engineering)
* How software fails: taxonomy of failure (implicit and explicit, fatal and non-fatal)
* Understanding software failure: the scientific method (including the roles of reproducibility, for testing hypotheses and gathering data)
Part 2: Approaches
* In situ debugging
-- Using Dynamic Tracing --Logging
-- Basic tools (e.g., finding information about what processes are doing?)
* Postmortem debugging (fatal failure)
Part 3: Specific expertise
These chapters start with narrative prose describing basic concepts, and then enumerate tips and techniques related to the problem space.
* Debugging memory issues in native code (corruption, use-after-free)
* Debugging resource exhaustion in native code
* Debugging multi-threaded programs
* Debugging in dynamic environments (including GC-related issues)
* Debugging the network (including TCP issues, jumbo frames, partitions)
* Debugging distributed systems
* Debugging performance issues
* Debugging psychotic issues
Part 4: Advanced topics
* Debugging-driven development (embracing debugging at development-time)
* What to do when you're stuck
* Debugging unfamiliar systems
* Debugging during an outage
* Building an organization for debugging
* Describing failure [rigorously, and the importance of it]
Este título pertence ao(s) assunto(s) indicados(s). Para ver outros títulos clique no assunto desejado.
debugging; breakpoints; stack tracing; core dumps; static code analysis; crash dump; divide-and-conquer; post-mortem debugging; Dtrace; debugging applications; debugging software
Draft table of contents
Part 1: Foundations
* Introduction (embracing debugging as both a first-class part of our jobs as engineers, and as an enjoyable, rewarding part of the craft of software engineering)
* How software fails: taxonomy of failure (implicit and explicit, fatal and non-fatal)
* Understanding software failure: the scientific method (including the roles of reproducibility, for testing hypotheses and gathering data)
Part 2: Approaches
* In situ debugging
-- Using Dynamic Tracing --Logging
-- Basic tools (e.g., finding information about what processes are doing?)
* Postmortem debugging (fatal failure)
Part 3: Specific expertise
These chapters start with narrative prose describing basic concepts, and then enumerate tips and techniques related to the problem space.
* Debugging memory issues in native code (corruption, use-after-free)
* Debugging resource exhaustion in native code
* Debugging multi-threaded programs
* Debugging in dynamic environments (including GC-related issues)
* Debugging the network (including TCP issues, jumbo frames, partitions)
* Debugging distributed systems
* Debugging performance issues
* Debugging psychotic issues
Part 4: Advanced topics
* Debugging-driven development (embracing debugging at development-time)
* What to do when you're stuck
* Debugging unfamiliar systems
* Debugging during an outage
* Building an organization for debugging
* Describing failure [rigorously, and the importance of it]
Part 1: Foundations
* Introduction (embracing debugging as both a first-class part of our jobs as engineers, and as an enjoyable, rewarding part of the craft of software engineering)
* How software fails: taxonomy of failure (implicit and explicit, fatal and non-fatal)
* Understanding software failure: the scientific method (including the roles of reproducibility, for testing hypotheses and gathering data)
Part 2: Approaches
* In situ debugging
-- Using Dynamic Tracing --Logging
-- Basic tools (e.g., finding information about what processes are doing?)
* Postmortem debugging (fatal failure)
Part 3: Specific expertise
These chapters start with narrative prose describing basic concepts, and then enumerate tips and techniques related to the problem space.
* Debugging memory issues in native code (corruption, use-after-free)
* Debugging resource exhaustion in native code
* Debugging multi-threaded programs
* Debugging in dynamic environments (including GC-related issues)
* Debugging the network (including TCP issues, jumbo frames, partitions)
* Debugging distributed systems
* Debugging performance issues
* Debugging psychotic issues
Part 4: Advanced topics
* Debugging-driven development (embracing debugging at development-time)
* What to do when you're stuck
* Debugging unfamiliar systems
* Debugging during an outage
* Building an organization for debugging
* Describing failure [rigorously, and the importance of it]
Este título pertence ao(s) assunto(s) indicados(s). Para ver outros títulos clique no assunto desejado.