ios: Correct typo in client API StartProcessingPendingReports.

Change-Id: Ibc40751a21ed884bde7ed592df20d7541762cba8
Reviewed-on: https://chromium-review.googlesource.com/c/crashpad/crashpad/+/3031701
Reviewed-by: Mark Mentovai <mark@chromium.org>
Commit-Queue: Justin Cohen <justincohen@chromium.org>
This commit is contained in:
Justin Cohen 2021-07-15 10:27:47 -04:00 committed by Crashpad LUCI CQ
parent 202283a85c
commit b8a1685773
3 changed files with 4 additions and 4 deletions

View File

@ -506,11 +506,11 @@ class CrashpadClient {
//! on another thread. This method does not block.
//!
//! A handler must have already been installed before calling this method.
static void StartProcesingPendingReports();
static void StartProcessingPendingReports();
//! \brief Requests that the handler capture an intermediate dump even though
//! there hasn't been a crash. The intermediate dump will be converted
//! to a mindump immediately. If StartProcesingPendingReports() has been
//! to a mindump immediately. If StartProcessingPendingReports() has been
//! called, this will also trigger an upload.
//!
//! For internal use only. Clients should use CRASHPAD_SIMULATE_CRASH().

View File

@ -233,7 +233,7 @@ void CrashpadClient::ProcessIntermediateDump(
}
// static
void CrashpadClient::StartProcesingPendingReports() {
void CrashpadClient::StartProcessingPendingReports() {
// TODO(justincohen): Start the CrashReportUploadThread.
}

View File

@ -96,7 +96,7 @@ the next call to `ProcessIntermediateDumps`. Conversely,
stability concerns. In this case, intermediate dumps are automatically
converted to minidumps and immediately eligible for uploading.
### `StartProcesingPendingReports`
### `StartProcessingPendingReports`
For similar reasons, applications may choose the correct time to begin uploading
pending reports, such as when ideal network conditions exist. By default,
clients start with uploading disabled. Applications should call this API when