You're reading from Mastering Embedded Linux Programming Create fast and reliable embedded solutions with Linux 5.4 and the Yocto Project 3.1 (Dunfell)

Product type Paperback

Published in May 2021

Publisher Packt

ISBN-13 9781789530384

Length 758 pages

Edition 3rd Edition

Languages

C++

Tools

Linux

Concepts

Embedded Systems

Authors (2):

Frank Vasquez

Mr. Chris Simmonds

View More author details

Table of Contents (27) Chapters

Preface

1. Section 1: Elements of Embedded Linux

2. Chapter 1: Starting Out FREE CHAPTER

3. Chapter 2: Learning about Toolchains

4. Chapter 3: All about Bootloaders

5. Chapter 4: Configuring and Building the Kernel

6. Chapter 5: Building a Root Filesystem

7. Chapter 6: Selecting a Build System

8. Chapter 7: Developing with Yocto

9. Chapter 8: Yocto Under the Hood

10. Section 2: System Architecture and Design Decisions

11. Chapter 9: Creating a Storage Strategy

12. Chapter 10: Updating Software in the Field

13. Chapter 11: Interfacing with Device Drivers

14. Chapter 12: Prototyping with Breakout Boards

15. Chapter 13: Starting Up – The init Program

16. Chapter 14: Starting with BusyBox runit

17. Chapter 15: Managing Power

18. Section 3: Writing Embedded Applications

19. Chapter 16: Packaging Python

20. Chapter 17: Learning about Processes and Threads

21. Chapter 18: Managing Memory

22. Section 4: Debugging and Optimizing Performance

23. Chapter 19: Debugging with GDB

24. Chapter 20: Profiling and Tracing

25. Chapter 21: Real-Time Programming

26. Other Books You May Enjoy

Summary

Knowing how to use GDB for interactive debugging is a useful tool in the embedded system developer's tool chest. It is a stable, well-documented, and well-known entity. It has the ability to debug remotely by placing an agent on the target, be it gdbserver for applications or kgdb for kernel code, and although the default command-line user interface takes a while to get used to, there are many alternative frontends. The three I mentioned were TUI, DDD, and Visual Studio Code. Eclipse is another popular frontend that supports debugging with GDB by way of the CDT plugin. I will refer you to the references in the Further reading section for information on how to configure CDT to work with a cross toolchain and connect to a remote device.

A second and equally important way to approach debugging is to collect crash reports and analyze them offline. In this category, we looked at application core dumps and kernel Oops messages.

However, this is only one way of identifying...