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.

…able overlay

Refactor the wasm symbolicator to make its DWARF workaround explicit
and unconditional. addr2line.py runs one llvm-symbolizer -f -i call
per address, then overlays the outermost frame's function name from a
startup-built DWARF interval table.

The overlay exists because llvm-symbolizer returns the wrong outermost
function name on wasm targets for two independent, source-verified
reasons:

- Symbol-table override on the outermost frame (LLVM design, not a
  bug). symbolizeInlinedCode in llvm/lib/DebugInfo/Symbolize/
  SymbolizableObjectFile.cpp unconditionally rewrites the outermost
  frame's FunctionName from getNameFromSymbolTable when
  FunctionNameKind::LinkageName and UseSymbolTable are both set, which
  is the default. Inline frames come from getInliningInfoForAddress
  (a different code path) and are provably immune.

- AddrDieMap invariant violation from wasm-opt -Oz -g DCE ghosts.
  LocationUpdater::getNewFuncStart in binaryen's src/wasm/wasm-debug.cpp
  returns 0 as a tombstone when an old address doesn't map to a
  surviving IR node, and updateDIE writes it into DW_AT_low_pc without
  removing the DW_TAG_subprogram. LLVM's updateAddressDieMap in
  DWARFUnit.cpp requires child ranges ⊆ parent ranges; these ghosts
  break that invariant so the map's upper_bound − 1 lookup returns
  an insertion-order-dependent DIE.

Both mechanisms produce the same "wrong outermost frame name" symptom
and both apply on any supported wasi-sdk, so the overlay runs on every
resolution. build_subprogram_intervals filters three DIE classes at
parse time: DW_AT_declaration=true (forward decls), low_pc == 0
(DWARF Code-section-relative zero is the function-count LEB, not a
real body — this is the DCE-ghost pattern), and high_pc <= low_pc
(degenerate ranges). The innermost covering DW_TAG_subprogram wins.

Also includes accumulated tool 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

Full design rationale, source citations, and empirical truth table in
test-tools/addr2line/README.md.
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