diff options
| author | Igor Kudrin <ikudrin@accesssoftek.com> | 2025-08-13 14:15:45 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-08-13 14:15:45 -0700 |
| commit | 36c2a6696853020ffc0072566b1f5e77efe96d0c (patch) | |
| tree | b4cd62cc1d6bf0ca415a39000eb5f6260a499a73 /llvm/lib/ObjCopy/ELF/ELFObject.cpp | |
| parent | 8061cae756aecf0da689ba31e0e14bf2b37b5e7f (diff) | |
| download | llvm-36c2a6696853020ffc0072566b1f5e77efe96d0c.zip llvm-36c2a6696853020ffc0072566b1f5e77efe96d0c.tar.gz llvm-36c2a6696853020ffc0072566b1f5e77efe96d0c.tar.bz2 | |
[lldb][test] Make TestFindRangesInMemory.py more robust (#152817)
`GetHeapRanges()` could return two overlapping ranges because it did not
check whether `heap_pointer1` lies within the range returned for
`heap_pointer2`. This could result in a test failure in
`test_find_ranges_in_memory_two_matches` when
`process.FindRangesInMemory()` returned 3 instead of 2.
The patch ensures that `GetHeapRanges()` returns either two
non-overlapping ranges or one range covering both heap pointers.
The issue was probably introduced in #111951
Diffstat (limited to 'llvm/lib/ObjCopy/ELF/ELFObject.cpp')
0 files changed, 0 insertions, 0 deletions