clayborg wrote:
What is the status of this PR? I think we will want this to make sure we don't
spam too many individual progress events. It can also be adpated for the new
categories after it goes in.
https://github.com/llvm/llvm-project/pull/75769
_
@@ -1430,6 +1445,279 @@ void Debugger::SetDestroyCallback(
m_destroy_callback_baton = baton;
}
+
+ /// Notify the progress thread that there is new progress data.
+void Debugger::NotifyProgress(std::unique_ptr &data_up) {
+ // Start the progress thread if it isn't already
@@ -1430,6 +1445,279 @@ void Debugger::SetDestroyCallback(
m_destroy_callback_baton = baton;
}
+
+ /// Notify the progress thread that there is new progress data.
+void Debugger::NotifyProgress(std::unique_ptr &data_up) {
+ // Start the progress thread if it isn't already
github-actions[bot] wrote:
:warning: C/C++ code formatter, clang-format found issues in your code.
:warning:
You can test this locally with the following command:
``bash
git-clang-format --diff 2aaeef1fad0c1b233f6d3ca67a6c05877dc9e998
598115f4d8240b6199493e6380369b0074af8411 --
llvmbot wrote:
@llvm/pr-subscribers-lldb
Author: Greg Clayton (clayborg)
Changes
Currently in LLDB if clients listen for Debugger::eBroadcastBitProgress events,
this can cause too many progress events to get sent to clients which makes the
feature a bit less useful that originally planne
https://github.com/clayborg created
https://github.com/llvm/llvm-project/pull/75769
Currently in LLDB if clients listen for Debugger::eBroadcastBitProgress events,
this can cause too many progress events to get sent to clients which makes the
feature a bit less useful that originally planned.
