diff options
| author | alx32 <103613512+alx32@users.noreply.github.com> | 2024-10-04 21:48:09 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-10-04 21:48:09 -0700 |
| commit | 9e862ae3219b09283971ca0ced52a64b0d6db86b (patch) | |
| tree | c6c3b53ae3f9a50b992d68378fb2a5eb13aca099 /lldb/source/Commands/CommandObjectSession.cpp | |
| parent | bf895c714e1f8a51c1e565a75acf60bf7197be51 (diff) | |
| download | llvm-9e862ae3219b09283971ca0ced52a64b0d6db86b.zip llvm-9e862ae3219b09283971ca0ced52a64b0d6db86b.tar.gz llvm-9e862ae3219b09283971ca0ced52a64b0d6db86b.tar.bz2 | |
[lld-macho] Fix invalid DWARF with --icf=safe_thunks (#111097)
There is a bug in the current implementation of `--icf=safe_thunks`
where a STABS entry is emitted for generated thunks. This is problematic
as we end up generating invalid DWARF as dsymutil will think the entire
function body is at the thunk location, when in actuality there will
only be a single branch present. This will end up causing overlapping
DWARF entries.
To fix this we never generate STABS entries for such thunks.
The existing `--icf=safe_thunks` test is updated to also generate debug
info and we add a check that no corrupt DWARF is generated.
As a future TODO we need to make `--keep-icf-stabs` compatible with
`--icf=safe_thunks`.
Diffstat (limited to 'lldb/source/Commands/CommandObjectSession.cpp')
0 files changed, 0 insertions, 0 deletions