[Lldb-commits] [lldb] [llvm] [llvm][lldb] Handle oversized LEB128 operands in DWARF expressions (PR #219149)

[via lldb-commits]

MrEven132 wrote:

> I'm still not certain I follow why only certain errors are handled in certain places, it seems like at any point where an Op is in an error state it should be OK to return

Thanks for raising this. The distinction is intentional for the issue being fixed (#202293): when a known operation has an LEB128 operand wider than an address, LLDB can consume the complete encoding, truncate the operand as required, report an `OperandDecode` error, and continue parsing subsequent operators. 
An `UnknownOperation` is different because its operand layout and end offset are unknown, so parsing cannot safely continue.

I’ll address the other inline code comments in the next update.

https://github.com/llvm/llvm-project/pull/219149