Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Book Overview & Buying Linux Kernel Debugging
  • Table Of Contents Toc
  • Feedback & Rating feedback
Linux Kernel Debugging

Linux Kernel Debugging

By : Kaiwan N. Billimoria
4.8 (6)
close
close
Linux Kernel Debugging

Linux Kernel Debugging

4.8 (6)
By: Kaiwan N. Billimoria

Overview of this book

The Linux kernel is at the very core of arguably the world’s best production-quality OS. Debugging it, though, can be a complex endeavor. Linux Kernel Debugging is a comprehensive guide to learning all about advanced kernel debugging. This book covers many areas in-depth, such as instrumentation-based debugging techniques (printk and the dynamic debug framework), and shows you how to use Kprobes. Memory-related bugs tend to be a nightmare – two chapters are packed with tools and techniques devoted to debugging them. When the kernel gifts you an Oops, how exactly do you interpret it to be able to debug the underlying issue? We’ve got you covered. Concurrency tends to be an inherently complex topic, so a chapter on lock debugging will help you to learn precisely what data races are, including using KCSAN to detect them. Some thorny issues, both debug- and performance-wise, require detailed kernel-level tracing; you’ll learn to wield the impressive power of Ftrace and its frontends. You’ll also discover how to handle kernel lockups, hangs, and the dreaded kernel panic, as well as leverage the venerable GDB tool within the kernel (KGDB), along with much more. By the end of this book, you will have at your disposal a wide range of powerful kernel debugging tools and techniques, along with a keen sense of when to use which.
Table of Contents (17 chapters)
close
close
1
Part 1: A General Introduction and Approaches to Kernel Debugging
4
Part 2: Kernel and Driver Debugging Tools and Techniques
11
Part 3: Additional Kernel Debugging Tools and Techniques

An introduction to the kdump/crash framework

When a userspace application (a process) crashes, it's often feasible to enable the kernel core dump feature; this allows the kernel to capture relevant segments (mappings) of the process virtual address space (VAS), and write them to a file that is traditionally named core. On Linux, the name – and indeed various features – are now settable (look up the man page on core(5) for details). How does this help? You can later examine and analyze the core dump using the GNU debugger (GDB) (the syntax is gdb -c core-dump-file original-binary-executable); it can help to find the root cause of the issue! This is called post-mortem analysis, as it's done upon the dead body of the process, which is the core dump image file.

That's great, but wouldn't it be useful to be able to do the same with the kernel? This is precisely what the kernel dump (kdump) infrastructure provides – the ability to collect and capture...

Unlock full access

Continue reading for free

A Packt free trial gives you instant online access to our library of over 7000 practical eBooks and videos, constantly updated with the latest in tech

Create a Note

Modal Close icon
You need to login to use this feature.
notes
bookmark search playlist download font-size

Change the font size

margin-width

Change margin width

day-mode

Change background colour

Close icon Search
Country selected

Close icon Your notes and bookmarks

Delete Bookmark

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete

Delete Note

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete

Confirmation

Modal Close icon
claim successful

Buy this book with your credits?

Modal Close icon
Are you sure you want to buy this book with one of your credits?
Close
YES, BUY