Menu
Use for Linux C/C++ GDB crash, core dump, and hang debugging.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Configure clangd language server for Zephyr RTOS projects with cross-compilation toolchains. Use when setting up clangd for Zephyr, nRF Connect SDK, or ARM cross-compilation projects, or when clangd shows errors like "Unknown Arm architecture profile" or "failed to resolve include".
Use when debugging embedded firmware through SEGGER J-Link RTT - capture RTT output, send RTT console commands, or open an interactive RTT console.
Use for MCU firmware debugging with GDB/gdbserver, probe or QEMU targets, flash/attach flows, and Cortex-M fault analysis.
Use when committing staged changes with a Conventional Commit.
Use when starting any coding task with unclear requirements, vague feature requests, or ambiguous bug fixes - before writing implementation code. Triggers automatic domain inference (Embedded, Python, DevOps, Zephyr, etc.) and compiles rigorous Markdown prompts with reconnaissance, HITL clarification, TDD workflow, and selectively applied domain constraints.
| name | linux-gdb-debugger |
| description | Use for Linux C/C++ GDB crash, core dump, and hang debugging. |
Use GDB evidence before editing Linux user-space C/C++ crash or hang bugs.
Use for local Linux executables, native tests, Linux core files, and user-provided Linux PIDs. This includes SIGSEGV, SIGABRT, bad pointers, memory corruption, deadlocks, infinite loops, JNI/native-extension crashes, and logic bugs that need bounded stepping.
Do not use for Windows, macOS/LLDB, MCU/OpenOCD/pyOCD/J-Link, RTOS targets, Linux kernel/module debugging, or remote gdbserver workflows.
scripts/ directory..debug/ GDB log.If symbols are missing or values show <optimized out>, say so and prefer Debug or RelWithDebInfo builds.
For direct C/C++ builds, prefer:
CFLAGS="-g -O0" CXXFLAGS="-g -O0"
For CMake:
cmake -S . -B build -DCMAKE_BUILD_TYPE=Debug
cmake --build build
If optimization is required to reproduce:
cmake -S . -B build -DCMAKE_BUILD_TYPE=RelWithDebInfo
cmake --build build
scripts/gdb-crash.sh <executable> [args...]STDIN=input.txt scripts/gdb-crash.sh <executable> [args...]scripts/gdb-core.sh <executable> <core-file>scripts/gdb-hang.sh <executable> [args...]PID=<pid> scripts/gdb-hang.sh [matching-executable]BREAK=main STEPS=30 MODE=next scripts/gdb-step.sh <executable> [args...]For noisy hang logs, use BT_COMMAND="thread apply all bt 30" or FRAME_ARGS=scalars.
Load only what is needed:
references/diagnosis-playbook.md for root-cause workflow.references/gdb-command-patterns.md for breakpoints, watchpoints, and stepping.references/common-native-bugs.md for failure signatures.sudo or destructive commands..debug/.STEPS; prefer breakpoints/watchpoints over long step runs.