Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Mastering Embedded Linux Programming

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)

Arrow left icon
Product type Paperback
Published in May 2021
Publisher Packt
ISBN-13 9781789530384
Length 758 pages
Edition 3rd Edition
Languages
Tools
Arrow right icon
Authors (2):
Arrow left icon
Frank Vasquez Frank Vasquez
Author Profile Icon Frank Vasquez
Frank Vasquez
Mr. Chris Simmonds Mr. Chris Simmonds
Author Profile Icon Mr. Chris Simmonds
Mr. Chris Simmonds
Arrow right icon
View More author details
Toc

Table of Contents (27) Chapters Close

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

Preparing to debug

You need to compile the code you want to debug with debug symbols. GCC offers two options for this: -g and -ggdb. The latter adds debug information that is specific to GDB, whereas the former generates information in an appropriate format for whichever target operating system you are using, making it the more portable option. In our particular case, the target operating system is always Linux, and it makes little difference whether you use -g or -ggdb. Of more interest is the fact that both options allow you to specify the level of debug information, from 0 to 3:

  • 0: This produces no debug information at all and is equivalent to omitting the -g or -ggdb switch.
  • 1: This produces minimal information, but includes function names and external variables, which is enough to generate a backtrace.
  • 2: This is the default and includes information about local variables and line numbers so that you can perform source-level debugging and single-step through the...
lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at €18.99/month. Cancel anytime