mirror of
https://github.com/dragonpilot/dragonpilot.git
synced 2026-06-20 13:32:04 +08:00
Vehicle Researcher
6adb63b915
date: 2026-06-04T09:49:56 master commit: c0ab3550eca2e9daf197c46b7e4b24aa9637cf2e
30 lines
1.2 KiB
Markdown
30 lines
1.2 KiB
Markdown
# Debugging Panda Safety with Replay Drive + LLDB
|
|
|
|
## 1. Start the debugger in VS Code
|
|
|
|
* Select **Replay drive + Safety LLDB**.
|
|
* Enter the route or segment when prompted.
|
|
[<img src="https://github.com/user-attachments/assets/b0cc320a-083e-46a7-a9f8-ca775bbe5604">](https://github.com/user-attachments/assets/b0cc320a-083e-46a7-a9f8-ca775bbe5604)
|
|
|
|
## 2. Attach LLDB
|
|
|
|
* When prompted, pick the running **`replay_drive` process**.
|
|
* ⚠️ Attach quickly, or `replay_drive` will start consuming messages.
|
|
|
|
> [!TIP]
|
|
> Add a Python breakpoint at the start of `replay_drive.py` to pause execution and give yourself time to attach LLDB.
|
|
|
|
## 3. Set breakpoints in VS Code
|
|
Breakpoints can be set directly in `modes/xxx.h` (or any C file).
|
|
No extra LLDB commands are required — just place breakpoints in the editor.
|
|
|
|
## 4. Resume execution
|
|
Once attached, you can step through both Python (on the replay) and C safety code as CAN logs are replayed.
|
|
|
|
> [!NOTE]
|
|
> * Use short routes for quicker iteration.
|
|
> * Pause `replay_drive` early to avoid wasting log messages.
|
|
|
|
## Video
|
|
|
|
View a demo of this workflow on the PR that added it: https://github.com/commaai/openpilot/pull/36055#issue-3352911578 |