More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    DWARF Expert: Read the Map Between Binary and Source

    1

    Interrogate DWARF debug info — DIE trees, address-to-line mapping, integrity checks, and parsing code with libdwarf, pyelftools, or gimli.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    DWARF Expert: Read the Map Between Binary and Source

    DWARF Expert: Read the Map Between Binary and Source

    Example session with this skill installed

    A crash report points at address 0x12340 in our binary. What function is that, what are its parameters, and is the debug info trustworthy?

    • Read your context and instructions
    • Compiled the dwarf expert

    Address 0x12340 traced. Tools: llvm-dwarfdump confirmed, ELF binary. Line program: address maps to parse_header in the parser source file. DIE: DW_TAG_subprogram parse_header, address range covering 0x12340, with two formal parameters — buf (pointer type, location recorded) and len (unsigned int). Source line identified from the line program. Verification: llvm-dwarfdump --verify passes, so the map is intact and the answer stands. Everything quoted from DIE attributes or line-program entries; function, parameters, line, and verify result saved with the case notes. The verification step matters as much as the trace: llvm-dwarfdump --verify passed, which means the DIE tree, the cross-references, and the line program are all internally consistent, so the function name, the parameter types, and the source line can all be trusted. The case notes record the tool versions used (llvm-dwarfdump and pyelftools) so the trace can be reproduced exactly. What DWARF could not answer is also recorded: the values of the parameters at crash time are not in the debug info, and only a core dump or a live session would supply them. The working log holds the tool versions, the DIE attributes quoted, and the verify result, so the trace can be reproduced exactly by anyone who picks the case up later. Rubric score: 8/8.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    DWARF is the map between a binary and the source that produced it: which address belongs to which function, which variable lives where, which line a crash address corresponds to. When the map is wrong or missing, debugging goes blind. This skill covers reading that map, searching it, verifying it, and building on it: which dwarfdump you actually have (libdwarf's and LLVM's differ), the DIE tree and what each entry means, escalating a search from address to symbol to scope, verifying debug-info integrity with llvm-dwarfdump, and writing parsing code with pyelftools or gimli. It includes the platform gotchas that waste hours — macOS keeps DWARF in .dSYM bundles, not the executable, and pyelftools is ELF-only. A worked example traces a crash address to a function, its parameters, and its source line, then verifies the info is intact. Out of scope: live debugging (gdb and lldb own that) and reversing beyond the debug sections.

    DWARF cannot answer questions about optimized-away variables or code built without debug info.

    • pyelftools is ELF-only; Mach-O work needs the LLVM tools.
    • A present-but-corrupt DWARF tree reads plausibly until verified — verification is not optional.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 3 days ago

    Permissions

    No special permissions declared or detected

    Listed3 days ago

    What's inside

    Frequently Asked Questions

    Run `dwarfdump --version` first. libdwarf's and LLVM's take different flags, and using one set against the other looks like a broken binary. Confirm the implementation, then use its flags.

    Linked Mach-O executables do not carry it — it stays in the object files until dsymutil collects it into a .dSYM bundle. Point your tools at the dSYM, not the executable.

    Usually not — the variable was optimized away. That is a real answer, not a failure. Record it as optimized away and move to the disassembly if you need the value.