[all-commits] [llvm/llvm-project] c50cba: [LLDB][SBSaveCore] Sbsavecore subregions bug (#138...

[Jacob Lalonde via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: c50cba6275271fba69be661b9ec0665b2be88dbc
      https://github.com/llvm/llvm-project/commit/c50cba6275271fba69be661b9ec0665b2be88dbc
  Author: Jacob Lalonde <jalalonde at fb.com>
  Date:   2025-05-05 (Mon, 05 May 2025)

  Changed paths:
    M lldb/include/lldb/Utility/RangeMap.h
    M lldb/source/Target/Process.cpp
    A lldb/test/API/functionalities/process_save_core_minidump/TestProcessSaveCoreMinidumpYaml.py
    A lldb/test/API/functionalities/process_save_core_minidump/minidump_mem64.yaml

  Log Message:
  -----------
  [LLDB][SBSaveCore] Sbsavecore subregions bug (#138206)

Custom regions in Process::GetUserSpecifiedCoreFileSaveRanges originally
used `FindEntryThatContains`. This made sense on my first attempt, but
what we really want are *intersecting* regions. This is so the user can
specify arbitrary memory, and if it's available we output it to the core
(Minidump or MachO).



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