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

Conceptually understanding how KGDB works

KGDB is a source-level debugger, allowing you to debug kernel (and module) code at the level of the C source file(s)!

Hang on a moment though. In order for an application process such as GDB to debug the kernel, it will need to halt the kernel's execution upon it hitting a breakpoint and while single-stepping code paths within the kernel. How is that possible? What will run the GDB process (and the rest of the system) then?

The reality is that GDB, supporting a client-server architecture, is used with two machines: one, a host system where the client GDB program runs (the one we're used to working with); the other, the target system, where the GDB server component is embedded into the kernel itself! (Unlike typical client/server apps, the GDB server component is the smaller of the two, and the GDB client is the relatively large one – the regular GDB program you're used to using.)

Figure 11...

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

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