diff options
| author | Jonas Devlieghere <jonas@devlieghere.com> | 2025-01-16 09:33:59 -0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-01-16 09:33:59 -0800 |
| commit | 8965dd40c63cf00610fcf550017b46dae736d94b (patch) | |
| tree | ec8e9d27b81723eb827c6057203ca88b2c7cab1f /lldb/source/Plugins/ScriptInterpreter/Python | |
| parent | 60e4d24963ebc256dd68f2f9d969ca8e52cd9649 (diff) | |
| download | llvm-8965dd40c63cf00610fcf550017b46dae736d94b.zip llvm-8965dd40c63cf00610fcf550017b46dae736d94b.tar.gz llvm-8965dd40c63cf00610fcf550017b46dae736d94b.tar.bz2 | |
[lldb] Handle a byte size of zero in CompilerType::GetValueAsScalar (#123107)
A bit or byte size of 0 is not a bug. It can legitimately (and
frequently) happen in Swift and C, just not in C++. However, it doesn't
make sense to read a scalar of zero bytes.
Currently, when this happens, we trigger an `lldb_assert` in the data
extractor and return 0, which isn't accurate. I have a bunch of reports
of the assert triggering, but nobody has been able to provide me with a
reproducer that I can turn into a test and I wasn't able to concoct a
test case by reverse-engineering the code.
rdar://141630334
Diffstat (limited to 'lldb/source/Plugins/ScriptInterpreter/Python')
0 files changed, 0 insertions, 0 deletions