[all-commits] [llvm/llvm-project] 17aca7: [lldb] Teach FuncUnwinders about discontinuous fun...

[Pavel Labath via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: 17aca79d98d92510d131c4766a040b02adf6c4b8
      https://github.com/llvm/llvm-project/commit/17aca79d98d92510d131c4766a040b02adf6c4b8
  Author: Pavel Labath <pavel at labath.sk>
  Date:   2025-03-27 (Thu, 27 Mar 2025)

  Changed paths:
    M lldb/include/lldb/Symbol/FuncUnwinders.h
    M lldb/include/lldb/Symbol/UnwindTable.h
    M lldb/source/Symbol/FuncUnwinders.cpp
    M lldb/source/Symbol/UnwindTable.cpp
    A lldb/test/Shell/Unwind/Inputs/basic-block-sections-with-dwarf.s
    A lldb/test/Shell/Unwind/Inputs/linux-x86_64.yaml
    A lldb/test/Shell/Unwind/basic-block-sections-with-dwarf-static.test
    A lldb/test/Shell/Unwind/basic-block-sections-with-dwarf.test

  Log Message:
  -----------
  [lldb] Teach FuncUnwinders about discontinuous functions (#133072)

The main change here is that we're now able to correctly look up plans
for these functions. Previously, due to caching, we could end up with
one entry covering most of the address space (because part of the
function was at the beginning and one at the end). Now, we can correctly
recognise that the part in between does not belong to that function, and
we can create a different FuncUnwinders instance for it. It doesn't help
the discontinuous function much (its plan will still be garbled), but
we can at least properly unwind out of the simple functions in between.

Fixing the unwind plans for discontinuous functions requires handling
each unwind source specially, and this setup allows us to make the
transition incrementally.



To unsubscribe from these emails, change your notification settings at https://github.com/llvm/llvm-project/settings/notifications