aboutsummaryrefslogtreecommitdiff
path: root/lldb/source/Plugins/ScriptInterpreter/Python/PythonReadline.h
diff options
context:
space:
mode:
authorDavid Spickett <david.spickett@linaro.org>2024-07-03 14:48:48 +0100
committerGitHub <noreply@github.com>2024-07-03 14:48:48 +0100
commit31015240d366e4bf6f114856caa6e9ce90742b7f (patch)
tree7b7a71113712cbf4706c3de82619f15dc6dabc83 /lldb/source/Plugins/ScriptInterpreter/Python/PythonReadline.h
parent41fddc4ec3302f125a5b84ae86c8027dedc89984 (diff)
downloadllvm-31015240d366e4bf6f114856caa6e9ce90742b7f.zip
llvm-31015240d366e4bf6f114856caa6e9ce90742b7f.tar.gz
llvm-31015240d366e4bf6f114856caa6e9ce90742b7f.tar.bz2
[lldb] Print "0x0" for bitfield like enums where the value is 0 (#97557)
Enums like this one are treated as bitfield like enums: enum FlagsLike {B=2, C=4}; lldb recognises them as collections of flags, so you can have "B | C". If there's any values not covered that's printed as hex "B | C | 0x1". What happened if the value was 0 was we would not match any of the enumerators, then the remainder check requires that the remainder is non-zero. So lldb would print nothing at all. Which I assume is a bug because knowing that no flags are set is useful, just as much as knowing that some unkown bit was set to make it non-zero.
Diffstat (limited to 'lldb/source/Plugins/ScriptInterpreter/Python/PythonReadline.h')
0 files changed, 0 insertions, 0 deletions