Geschäftskunden Kundenprogramme
Vor Ort
Merkzettel Warenkorb
Produktbild: Cantrill, B: Joy of Debugging, The

Cantrill, B: Joy of Debugging, The

Fr. 48.90

inkl. gesetzl. MwSt., Versandkostenfrei

Beschreibung

Produktdetails

Einband

Taschenbuch

Erscheinungsdatum

07.04.2025

Verlag

Addison Wesley Longman

Seitenzahl

500

Maße (L/B/H)

23.2/17.8/4 cm

Gewicht

1 g

Sprache

Englisch

ISBN

978-0-13-457872-9

Beschreibung

Produktdetails

Einband

Taschenbuch

Erscheinungsdatum

07.04.2025

Verlag

Addison Wesley Longman

Seitenzahl

500

Maße (L/B/H)

23.2/17.8/4 cm

Gewicht

1 g

Sprache

Englisch

ISBN

978-0-13-457872-9

Herstelleradresse

Pearson Education
St.-Martin-Str. 82, 81541 - DE, München
info@pearson.de

Noch keine Bewertungen vorhanden

Verfassen Sie die erste Bewertung zu diesem Artikel

Helfen Sie anderen Kundinnen und Kunden durch Ihre Meinung.

Kundinnen und Kunden meinen

Bewertungen (0)
  • Produktbild: Cantrill, B: Joy of Debugging, The

  • 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]