liveBook · Manning

What you will learn in Memory Safe C++

How to write safety-critical software

by Jean Frantz René · Manning Early Access Program (MEAP)

Chapter by chapter

Chapter 1: Real-time and safety-critical software

The section uses the CrowdStrike outage to contrast a recoverable software failure with the potentially irreversible consequences of memory errors in safety-critical systems.

1.1 Defining safety-critical software · 1.2 Defining real-time safety-critical software · 1.3 Different industries, same challenge · 1.4 The case for C++ · 1.4.1 Performance without overhead · 1.4.2 Deterministic execution · 1.4.3 Industry maturity · 1.5 Memory safety challenges · 1.6 The C++ safety paradox · 1.7 C++ memory safety triad · 1.8 The complete learning cycle (CLC) · 1.9 Tools and environment · 1.10 Summary

What you learn in chapter 1 →

Chapter 2: Standards, coding guidelines, and memory safety

This introduction explains why C++ compilation alone cannot ensure safety and how standards, coding guidelines, and independent assessment complement it.

2.1 The safety standards · 2.1.1 Automotive — ISO 26262 · 2.1.2 Medical devices — IEC 62304 · 2.1.3 Railway — EN 50716:2023 · 2.1.4 Aerospace — DO-178C · 2.1.5 Industrial — IEC 61508 · 2.2 C++ coding guidelines in practice · 2.3 From standards to memory-safe C++ · 2.4 Type of memory safety violations · 2.4.1 Spatial memory safety (The “where” question) · 2.4.2 Temporal memory safety (The “when” question) · 2.4.3 Both dimensions together · 2.5 The two categories of impacts · 2.6 Toward compiler-enforced memory safety · 2.7 Summary

What you learn in chapter 2 →

Concepts explained in this book

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.