diff options
| author | David Spickett <david.spickett@linaro.org> | 2025-09-25 10:58:19 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-09-25 10:58:19 +0100 |
| commit | bafcc3e3b3353718b47e77618f0bb5fad7d1aa15 (patch) | |
| tree | ba14adbb658bbb605f2b2cea8366605e892a23a2 /libcxx/include/__algorithm/reverse.h | |
| parent | 65b41f03b674872d95efda60877d5628c3b4ce9a (diff) | |
| download | llvm-bafcc3e3b3353718b47e77618f0bb5fad7d1aa15.zip llvm-bafcc3e3b3353718b47e77618f0bb5fad7d1aa15.tar.gz llvm-bafcc3e3b3353718b47e77618f0bb5fad7d1aa15.tar.bz2 | |
[lldb][test] Refactor and expand TestMemoryRegionDirtyPages.py (#156035)
This started as me being annoyed that I got loads of this when
inspecting memory regions on Mac:
Modified memory (dirty) page list provided, 0 entries.
So I thought I should test the existing behaviour, which led me to
refactor the existing test to run the same checks on all regions.
In the process I realised that the output is not wrong. There is a
difference between knowing that no pages are dirty and not knowing
anything about dirty pages. We print that there are 0 entries so the
user knows that difference.
The test case now checks "memory region" output as well as API use.
There were also some checks only run on certain regions, like page size,
which now run for all of them.
Diffstat (limited to 'libcxx/include/__algorithm/reverse.h')
0 files changed, 0 insertions, 0 deletions