domains / families / software-engineering / dwarf-expert

dwarf-expert

combined

Provides expertise for analyzing DWARF debug files and understanding the DWARF debug format/standard (v3-v5). Triggers when understanding DWARF information, interacting with DWARF files, answering DWARF-related questions, or working with code that parses DWARF data. Analyzes DWARF debug information in compiled binaries. Use when inspecting .debug_* sections, DIE trees, or DW_TAG_/DW_AT_ entries with dwarfdump/llvm-dwarfdump or readelf, verifying debug info with llvm-dwarfdump --verify, answering DWARF standard questions, or writing code that parses DWARF (libdwarf, pyelftools, gimli).

When to use

• Understanding or parsing DWARF debug information from compiled binaries
• Answering questions about the DWARF standard (v3, v4, v5)
• Writing or reviewing code that interacts with DWARF data
• Using `dwarfdump` or `readelf` to extract debug information
• Verifying DWARF data integrity with `llvm-dwarfdump --verify`
• Working with DWARF parsing libraries (libdwarf, pyelftools, gimli, etc.)

When not to use

• **DWARF v1/v2 Analysis**: Expertise limited to versions 3, 4, and 5.
• **General ELF Parsing**: Use standard ELF tools if DWARF data isn't needed.
• **Executable Debugging**: Use dedicated debugging tools (gdb, lldb, etc) for debugging executable code/runtime behavior.
• **Binary Reverse Engineering**: Use dedicated RE tools (Ghidra, IDA) unless specifically analyzing DWARF sections.
• **Compiler Debugging**: DWARF generation issues are compiler-specific, not covered here.
• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Skill page

Conflict

The trailofbits copy is the more complete, self-contained procedure: it contains the specific dwarfdump flags, the DIE search escalation strategy, the macOS dSYM caveat, the DWARF version pinning notes, and the library table with parsing pitfalls. The sickn33 copy is a wrapper that delegates the detailed steps to external reference files (readelf.md, dwarfdump.md, coding.md) and adds a decision tree and explicit scope limits (v3-v5 only). Because the sickn33 copy lacks the concrete command-line details and the trailofbits copy lacks the explicit version scope and decision-tree structure, crowning one would hide a real alternative approach (self-contained vs. reference-file-based).