[all-commits] [llvm/llvm-project] ff1c95: [LLDB] Detect Memory overlapping between AllocateM...

[aokblast via All-commits]

  Branch: refs/heads/users/aokblast/lldb/stop_id_guard
  Home:   https://github.com/llvm/llvm-project
  Commit: ff1c952537629af987c846f3447278767925688d
      https://github.com/llvm/llvm-project/commit/ff1c952537629af987c846f3447278767925688d
  Author: ShengYi Hung <aokblast at FreeBSD.org>
  Date:   2026-07-11 (Sat, 11 Jul 2026)

  Changed paths:
    M lldb/include/lldb/Expression/IRMemoryMap.h
    M lldb/source/Expression/IRInterpreter.cpp
    M lldb/source/Expression/IRMemoryMap.cpp

  Log Message:
  -----------
  [LLDB] Detect Memory overlapping between AllocateMemory and MemoryInfo

IRMemoryMap estimates a free address range using memory information.
However, the memory returns by AllocateMemory can overlap with the
ranges reported by MemoryInfo (internally backed by PT_VM_ENTRY),
because the kernel is unaware of allocations made during the probing
process.

As a result, two allocatios may silently insert duplicate key for
different objects, leading to intermittent test failure. The issue is
nodeterministic because it depends on the underlying malloc
implementation and ASLR.

Fix this by detecting overlapping allocations after AllocateMemory. If
an overlap is found, fall back to the address-guessing path, which
perform the necessary overlap checks before committing the allocation.

Also, return and print  message in IRInterpreter in unsecessful allocation.



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