[lldb][tests] Automatically call compute_mydir (NFC)Eliminate boilerplate of having each test manually assign to `mydir` by calling`compute_mydir` in lldbtest.py.Differential Revision: https://r
[lldb][tests] Automatically call compute_mydir (NFC)Eliminate boilerplate of having each test manually assign to `mydir` by calling`compute_mydir` in lldbtest.py.Differential Revision: https://reviews.llvm.org/D128077
show more ...
[lldb][AArch64] Don't check for VmFlags in smaps filesAArch64 kernel builds default to having /smaps andthe "VmFlags" line was added in 3.8. Long before MTEwas supported.So we can assume that i
[lldb][AArch64] Don't check for VmFlags in smaps filesAArch64 kernel builds default to having /smaps andthe "VmFlags" line was added in 3.8. Long before MTEwas supported.So we can assume that if you're AArch64 with MTE,you can run this test.The previous method of checking had a race conditionwhere the process we read smaps for, could finish beforewe get to read the file.I explored some alternatives but in the end I thinkit's fine to just assume we have what we need.Reviewed By: omjavaidDifferential Revision: https://reviews.llvm.org/D100493
[lldb][AArch64] Simplify MTE memory region testBy checking for cpu and toolchain features aheadof time we don't need the custom return codes.Reviewed By: omjavaidDifferential Revision: https:/
[lldb][AArch64] Simplify MTE memory region testBy checking for cpu and toolchain features aheadof time we don't need the custom return codes.Reviewed By: omjavaidDifferential Revision: https://reviews.llvm.org/D97684
[lldb][AArch64] Only run MTE memory region test if we have MTEThis test is flakey because it tries to read the proc/smapsfile of the first lldb-server process it finds. This processcan finish bef
[lldb][AArch64] Only run MTE memory region test if we have MTEThis test is flakey because it tries to read the proc/smapsfile of the first lldb-server process it finds. This processcan finish before we finish doing that.http://lab.llvm.org:8011/#/builders/96/builds/6634/steps/6/logs/stdioFor now limit this to MTE targets which basically meansQEMU via lldb-dotest, which doesn't have this issue.I'll fix the race condition shortly.
[lldb][AArch64/Linux] Show memory tagged memory regionsThis extends the "memory region" command toshow tagged regions on AArch64 Linux when the MTEextension is enabled.(lldb) memory region the_
[lldb][AArch64/Linux] Show memory tagged memory regionsThis extends the "memory region" command toshow tagged regions on AArch64 Linux when the MTEextension is enabled.(lldb) memory region the_page[0x0000fffff7ff8000-0x0000fffff7ff9000) rw-memory tagging: enabledThis is done by adding an optional "flags" field tothe qMemoryRegion packet. The only supported flag is"mt" but this can be extended.This "mt" flag is read from /proc/{pid}/smaps on Linux,other platforms will leave out the "flags" field.Where this "mt" flag is received "memory region" willshow that it is enabled. If it is not or the targetdoesn't support memory tagging, the line is not shown.(since majority of the time tagging will not be enabled)Testing is added for the existing /proc/{pid}/mapsparsing and the new smaps parsing.Minidump parsing has been updated where needed,though it only uses maps not smaps.Target specific tests can be run with QEMU and I haveadded MTE flags to the existing helper scripts.Reviewed By: labathDifferential Revision: https://reviews.llvm.org/D87442