diff options
| author | Dayann D'almeida <dayannd@google.com> | 2023-07-11 16:50:28 -0700 |
|---|---|---|
| committer | Mircea Trofin <mtrofin@google.com> | 2023-07-11 17:07:29 -0700 |
| commit | a1e80acc6314066aeb55117127e1939d451bbc71 (patch) | |
| tree | af96f0de846cd0c25225567d0d58405082bdbbc2 /lldb/source/Plugins/ScriptInterpreter/Python/SWIGPythonBridge.h | |
| parent | 875b881186c4eb146e77e76ad72ee0a356d7c69f (diff) | |
| download | llvm-a1e80acc6314066aeb55117127e1939d451bbc71.zip llvm-a1e80acc6314066aeb55117127e1939d451bbc71.tar.gz llvm-a1e80acc6314066aeb55117127e1939d451bbc71.tar.bz2 | |
[Object] fixed invalid symbol handling in ELFObjectFile::getSymbolName
Found a bug in ElfObjectFile.h that occurred when there was an invalid Symbol Name in an object file. This error affected the behavior of the Expected<> value and leading it to abort, rather than behave as normal. I found this as I was adding tests to llvm-cm, as prompted by @jhenderson.
Without this fix, upon encountering an invalid symbol and trying tot l get its name, the program states that
```Expected<T> must be checked before access or destruction```
and aborts.
Reviewed By: MaskRay
Differential Revision: https://reviews.llvm.org/D154665
Diffstat (limited to 'lldb/source/Plugins/ScriptInterpreter/Python/SWIGPythonBridge.h')
0 files changed, 0 insertions, 0 deletions