[all-commits] [llvm/llvm-project] 7517a1: [LLDB][SBSaveCoreOptions] Add new API to expose th...

[Jacob Lalonde via All-commits]

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

  Changed paths:
    M lldb/bindings/interface/SBSaveCoreOptionsDocstrings.i
    M lldb/include/lldb/API/SBSaveCoreOptions.h
    M lldb/include/lldb/Symbol/SaveCoreOptions.h
    M lldb/source/API/SBSaveCoreOptions.cpp
    M lldb/source/Symbol/SaveCoreOptions.cpp
    M lldb/test/API/python_api/sbsavecoreoptions/TestSBSaveCoreOptions.py
    M lldb/test/API/python_api/sbsavecoreoptions/basic_minidump.yaml

  Log Message:
  -----------
  [LLDB][SBSaveCoreOptions] Add new API to expose the expected core size in bytes (#138169)

My current internal work requires some sensitivity to IO usage. I had a
work around to calculate the expected size of a Minidump, but I've added
this PR so an automated system could look at the expected size of an
LLDB generated Minidump and then choose if it has the space or wants to
generate it.

There are some prerequisites to calculating the correct size, so I have
the API take a reference for an SBError, I originally tried to return an
SBError and instead take a uint64_t reference, but this made the API
very difficult to use in python.

Added a test case as well.



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