aboutsummaryrefslogtreecommitdiff
path: root/lldb/source/Commands/CommandObjectCommands.cpp
diff options
context:
space:
mode:
authorAlex Langford <alangford@apple.com>2023-05-30 14:35:05 -0700
committerAlex Langford <alangford@apple.com>2023-06-06 10:50:54 -0700
commit6836a47b7e6b57927664ec6ec750ae37bb951129 (patch)
tree8188d0100dafde991291760a7df1d4bbeb0f1a48 /lldb/source/Commands/CommandObjectCommands.cpp
parentc1401e9f3e7cfe10d5c8d7d040d66898bbc8ef39 (diff)
downloadllvm-6836a47b7e6b57927664ec6ec750ae37bb951129.zip
llvm-6836a47b7e6b57927664ec6ec750ae37bb951129.tar.gz
llvm-6836a47b7e6b57927664ec6ec750ae37bb951129.tar.bz2
[DebugInfo] Add error checking around data extraction in DWARFAbbreviationDeclaration::extract
In trying to hoist errors further up this callstack, I discovered that if the data in the debug_abbrev section is invalid entirely, the code that parses the debug_abbrev section may do strange or unpredictable things. The underlying issue is that DataExtractor will return a value of 0 when it encounters an error in extracting a LEB128 value. It's thus difficult to determine if there was an error just by looking at the return value. This patch aims to bail at the first sight of an error in the debug_abbrev parsing code. Differential Revision: https://reviews.llvm.org/D151755
Diffstat (limited to 'lldb/source/Commands/CommandObjectCommands.cpp')
0 files changed, 0 insertions, 0 deletions