================
@@ -63,13 +68,30 @@ class Progress {
///
/// @param [in] title The title of this progress activity.
///
- /// @param [in] total The total units of work to be done if specified, if
- /// set to UINT64_MAX then an indeterminate progress indicator should be
+ /// @param [in] report_type Enum value indicating how the progress is being
+ /// reported. Progress reports considered "aggregate" are reports done for
+ /// operations that may happen multiple times during a debug session.
+ ///
+ /// For example, when a debug session is first started it needs to parse the
----------------
jasonmolenda wrote:
Is this the case that I attach to a running process and I find 100 binaries
loaded in the process. I create Module/ObjectFile's for each binary, including
parsing the symbol table, possibly looking for a dSYM or a dwp symbol file with
debug information for each of those. If dSYMs are an example of additional
binaries that may need to be scanned (and report progress as they're being
scanned), is it sufficient to simply mention how each of the hundred binaries
in the process will report a status update as its Module is created, and not
mention dSYMs specifically?
https://github.com/llvm/llvm-project/pull/69516
_______________________________________________
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
