[Lldb-commits] [PATCH] D77108: [lldb/DWARF] Fix evaluator crash when accessing empty stack
Adrian Prantl via Phabricator via lldb-commits
lldb-commits at lists.llvm.org
Tue Mar 31 09:58:14 PDT 2020
aprantl added a comment.
For the future, a clean solution would be extending the macros in Dwarf.def to list the stack effects in the definitions of the DW_OP_*, for example
// opcode, name, version, vendor, in, out
HANDLE_DW_OP(0x12, dup, 2, DWARF, 1, 2)
and then we could write a static verifier that ensures that the stack effects of an entire expression is sound. (And we could check this in LLVM, already, too).
Is there any DWARF operator where the stack effect (number of consumes & produced stack elements) isn't statically known?
rG LLVM Github Monorepo
CHANGES SINCE LAST ACTION
More information about the lldb-commits