Diagnose DOCA build, link, runtime, and driver failures using a layered debug ladder.
npx skills add https://github.com/NVIDIA/skills --skill doca-debug
Please help me install this Agent Skill. Skill: doca-debug Source: https://github.com/NVIDIA/skills/tree/main/skills/doca-debug Command: npx skills add https://github.com/NVIDIA/skills --skill doca-debug
Debugging NVIDIA DOCA applications is hard because symptoms like link errors, silent programs, or DOCA_ERROR_* return codes can originate at any of seven layers (install, version, build, link, runtime, program, driver). This Skill gives agents a canonical layered ladder and a 5-phase iterative debug loop so they identify the correct layer first, capture read-only evidence before mutating anything, and avoid wasted effort.
Ask your agent to help debug a DOCA symptom, for example: my DOCA program fails at the link step with undefined reference to doca_flow_init, walk me through which layer is responsible.
High-intent search queries and answers about installing and using this skill.
An undefined reference to a doca_* symbol is a Link-layer (layer 4) failure. Use pkg-config --libs doca-<library> verbatim for the link line instead of hand-typing -l flags, since libraries like DOCA Flow ship as multiple separate shared objects on recent versions.
Raise verbosity with --sdk-log-level 70 (TRACE) on the first run, or set DOCA_LOG_LEVEL for programs that read it. For deeper output, link against the doca-<library>-trace pkg-config module, which emits DEBUG and TRACE lines the release flavor never produces.
Container debug is limited: in-container dmesg, journalctl, and /sys show the container's view, not host kernel or hardware events. For symptoms involving real packets or devices, use a native install or a host shell before forming hardware hypotheses.
Route elsewhere for env-class symptoms like pkg-config failures or unmounted hugepages (doca-setup), DOCA_ERROR_* taxonomy and lifecycle interpretation (doca-programming-guide), and library-specific debug such as Flow pipe traces or RDMA queue-pair stats (the matching library skill).
Capture the read-only triple: program stdout/stderr with --sdk-log-level 70, the system view via dmesg and journalctl, and the DOCA view via doca_caps --list-devs plus pkg-config --modversion. State which ladder layer you reached and avoid internal hostnames or build numbers.
thuantan2060Structures root-cause investigation for unresolved technical failures using THOUGHT/ACTION/OBSERVATION cycles and verified evidence before implementation.
air-gappedAutomate NVIDIA datacenter GPU bring-up on Ubuntu 24.04 with health validation.
ZurybrDebug release-only crashes from custom memory heap and static destruction order.
MOODMNKY-LLCDebug Node.js runtime issues using the native inspector and Chrome DevTools Protocol.
