Skip to content

Addr2line enhance 3#4975

Open
TianlongLiang wants to merge 2 commits into
bytecodealliance:mainfrom
TianlongLiang:addr2line_enhance_3
Open

Addr2line enhance 3#4975
TianlongLiang wants to merge 2 commits into
bytecodealliance:mainfrom
TianlongLiang:addr2line_enhance_3

Conversation

@TianlongLiang

Copy link
Copy Markdown
Contributor

No description provided.

…lver

Refactor the wasm symbolicator to make its toolchain workarounds
explicit. addr2line.py now detects the wasi-sdk's clang major version
at startup and routes per-frame address resolution to one of:

- resolve_address_modern (clang >= 22, wasi-sdk 33+):
    single llvm-symbolizer call per address. The symbolizer handles
    address-to-name correctly on this clang.

- resolve_address_legacy (clang < 22 or unknown):
    llvm-symbolizer call + llvm-dwarfdump --lookup overlay to fix
    the outermost function name. Older clang versions emit wasm DWARF
    that confuses llvm-symbolizer's address-to-name resolver for some
    addresses (e.g., reports 'recurse' as 'free'). --lookup goes
    through a different DWARF traversal path that handles them.

The dispatch decision is logged once to stderr so users can see
which path was taken without polluting stdout. Stdout is byte-
identical between paths for non-buggy inputs.

Also includes accumulated improvements:
- --mode flag {interp,aot,fast-interp} for different runtime offset
  conventions (interp post-advance, aot at-instruction-start,
  fast-interp's transformed in-memory bytecode)
- Inline frame annotation "(inlined into <next>)" for clarity
- llvm-symbolizer preferred over llvm-addr2line for column info
- Fallback for offset=0 (trap at function entry; frame_ip not captured)
- Last-resort function-index name fallback when DWARF lacks PC ranges
New self-contained sample demonstrating the full production-debug
workflow for optimized WASM:

- 4-step build pipeline (clang -Oz -g -flto, wasm-opt -Oz -g, llvm-strip
  --strip-all, wamrc) producing prod.wasm + prod.aot + debug.wasm
  companion artifacts.
- Two test apps (oob, stackoverflow) split into multi-file C sources
  to exercise cross-TU LTO inlining.
- USE_FAST_INTERP CMake option to build iwasm in classic or fast-interp
  mode for testing.
- symbolicate.sh: end-to-end driver that runs iwasm on the prod binary,
  captures the call stack, and resolves it via addr2line.py + the
  debug companion. Auto-detects classic vs fast-interp from the iwasm
  binary.
- verify.sh: per-(app, mode) assertion that the symbolicated output
  contains the expected source files. Used by CI.

Depends on the addr2line.py refactor (--mode flag is invoked from
symbolicate.sh).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant