[all-commits] [llvm/llvm-project] 0e0127: [lldb] Fix vtable support on arm64e (#199116)

[Alex Langford via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: 0e0127e5b21dce0cf500e24467f1471d479876be
      https://github.com/llvm/llvm-project/commit/0e0127e5b21dce0cf500e24467f1471d479876be
  Author: Alex Langford <alangford at apple.com>
  Date:   2026-05-26 (Tue, 26 May 2026)

  Changed paths:
    M lldb/source/ValueObject/ValueObjectVTable.cpp
    M lldb/test/API/functionalities/vtable/TestVTableValue.py

  Log Message:
  -----------
  [lldb] Fix vtable support on arm64e (#199116)

There were 2 small issues.
1. ValueObjectVTableChild was not fixing the addresses it was pulling
from signed pointers. This broke things like `SBValue::GetLoadAddress`
and identifying the function pointer type from debug info.
2. TestVTableValue.py made a lot of assumptions that did not hold on
arm64e. a. GetValueAsUnsigned will return a raw pointer value. Most of
the time, we needed GetValueAsAddress. b. The test was reading pointers
out of memory without fixing them up. c. The summary for a function
pointer on arm64e includes the load address. This isn't true on other
platforms.



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