You're reading from Linux Kernel Debugging Leverage proven tools and advanced techniques to effectively debug Linux kernels and kernel modules

Product type Paperback

Published in Aug 2022

Publisher Packt

ISBN-13 9781801075039

Length 638 pages

Edition 1st Edition

Tools

Linux

Concepts

System Administration

Author (1):

Kaiwan N. Billimoria

View More author details

Table of Contents (17) Chapters

Preface

1. Part 1: A General Introduction and Approaches to Kernel Debugging

2. Chapter 1: A General Introduction to Debugging Software FREE CHAPTER

3. Chapter 2: Approaches to Kernel Debugging

4. Part 2: Kernel and Driver Debugging Tools and Techniques

5. Chapter 3: Debug via Instrumentation – printk and Friends

6. Chapter 4: Debug via Instrumentation – Kprobes

7. Chapter 5: Debugging Kernel Memory Issues – Part 1

8. Chapter 6: Debugging Kernel Memory Issues – Part 2

9. Chapter 7: Oops! Interpreting the Kernel Bug Diagnostic

10. Chapter 8: Lock Debugging

11. Part 3: Additional Kernel Debugging Tools and Techniques

12. Chapter 9: Tracing the Kernel Flow

13. Chapter 10: Kernel Panic, Lockups, and Hangs

14. Chapter 11: Using Kernel GDB (KGDB)

15. Chapter 12: A Few More Kernel Debugging Approaches

16. Other Books You May Enjoy

Building your kernel and modules with Clang

Low Level Virtual Machine (LLVM) is the original name given to this modular compiler tooling project. It now doesn't have much to do with traditional virtual machines and is instead a powerful backend for several compilers and toolchains.

Clang (the pronunciation rhymes with "slang") is a modern compiler frontend technology for C-type languages (includes support for C, C++, CUDA, Objective C/C++, and more) and is based on the LLVM compiler. It's considered a drop-in replacement for GCC. Clang currently seems to have a significant advantage over GCC – especially from our point of view – generating superior diagnostics as well as being able to intelligently generate code avoiding OOB accesses. This is critical. It paves the way to superior code. We saw (in the previous section on KASAN) that faulty left-OOB accesses on global memory, not reliably caught by GCC (versions 9.3, 10, and 11), are caught with...