[Lldb-commits] [PATCH] D85376: Fix how ValueObjectChild handles bit-fields stored in a Scalar in UpdateValue()

Pavel Labath via Phabricator via lldb-commits lldb-commits at lists.llvm.org
Tue Aug 11 05:04:53 PDT 2020

labath added a comment.

This manifested itself for variables in registers because those end up being described as `eValueTypeScalar`, is that so?

If that's the case, then I think this would also manifest for variables described via `DW_OP_constu 0xdead, DW_OP_stack_value`. And if *that* is true, then this could be tested a lot simpler by having a global variable described by DW_OP_stack_value and "target variable"-ing it -- no makefiles, no python, just a simple .s file. And it would run on all platforms, not just darwin.

`test/Shell/SymbolFile/DWARF/DW_OP_piece-struct.s` tests a very similar thing in precisely this way. I suspect you could just take that test as a template and replace the struct definition with one that contains bitfieds.



More information about the lldb-commits mailing list