aboutsummaryrefslogtreecommitdiff
path: root/lldb/source/Commands/CommandObjectThread.cpp
diff options
context:
space:
mode:
authorFelipe de Azevedo Piovezan <fpiovezan@apple.com>2025-09-04 13:05:10 -0700
committerGitHub <noreply@github.com>2025-09-04 13:05:10 -0700
commitf88eadda357b0429b390ec0bcf64c361ad1a8f28 (patch)
tree6750175e406c50139594ea17e75a4d0792c36fde /lldb/source/Commands/CommandObjectThread.cpp
parent9a3aedb093008b55fa2018396cebb9b4606a7453 (diff)
downloadllvm-f88eadda357b0429b390ec0bcf64c361ad1a8f28.zip
llvm-f88eadda357b0429b390ec0bcf64c361ad1a8f28.tar.gz
llvm-f88eadda357b0429b390ec0bcf64c361ad1a8f28.tar.bz2
[lldb] Call FixUpPointer in WritePointerToMemory (try 2) (#153585)
In architectures where pointers may contain metadata, such as arm64e, the metadata may need to be cleaned prior to sending this pointer to be used in expression evaluation generated code. This patch is a step towards allowing consumers of pointers to decide whether they want to keep or remove metadata, as opposed to discarding metadata at the moment pointers are created. See #150537. This was tested running the LLDB test suite on arm64e. (The first attempt at this patch caused a failure in TestScriptedProcessEmptyMemoryRegion.py. This test exercises a case where IRMemoryMap uses host memory in its allocations; pointers to such allocations should not be fixed, which is what the original patch failed to account for).
Diffstat (limited to 'lldb/source/Commands/CommandObjectThread.cpp')
0 files changed, 0 insertions, 0 deletions