Mastering Embedded Debugging (Part 2)

After your remote debugging connection is established, it’s time to solve real-world problems. In this second part, Christoph Sterz demonstrates how to use your remote debugging setup to act as if you were running the code directly on your desktop.

We dive into a real-world scenario: a ship navigation app that crashes on the target device. You'll see how to catch a segmentation fault, interpret stack traces, and identify common pitfalls like lambda lifetime issues in Qt. We also wrap up with QML profiling, showing you how to pinpoint performance bottlenecks and slow frames directly on the hardware.

This video covers:

- Remote GDB Workflow: Using target extended-remote to catch crashes in real-time.

- Debugging Case Study: Solving a classic lambda reference error that only crashes on hardware.

- QML Performance: How to profile startup costs and runtime frame rates on the device.

- Safety Warning: Best practices for enabling QML debugging in secure environments.

Chapters:

0:00 - Introduction

0:45 - Target-Specific Bugs

1:08 - Remote GDB Connection

2:07 - Capturing the Crash

3:13 - Enabling QML Debugging

3:47 - QML Performance Profiling

5:06 - Analyzing Profiler Data

5:35 - Summary

Links:

Mastering Embedded Debugging (Part 1)

All "Embedded with Qt" videos

About the host:

Christoph has been developing with C++ for over 15 years, and Qt for the last 10. A contributor to Gammaray, KDAB’s in-depth Qt-Analysis-Tool, Christoph specializes in performance optimization for embedded systems.