designdoc: Add description of user data sources.

Bug: crashpad:167
Change-Id: I8c5032d6710ea828e354103743d34772fd083958
Reviewed-on: https://chromium-review.googlesource.com/472947
Commit-Queue: Sigurður Ásgeirsson <siggi@chromium.org>
Reviewed-by: Mark Mentovai <mark@chromium.org>
This commit is contained in:
Sigurdur Asgeirsson 2017-04-12 08:49:16 -04:00 committed by Commit Bot
parent 79425e4d97
commit 1f28a123a4

View File

@ -452,6 +452,8 @@ suspend and resume and such.
### Extensibility ### Extensibility
#### Client Extensibility
Clients are able to extend the generated crash reports in two ways, by Clients are able to extend the generated crash reports in two ways, by
manipulating their CrashpadInfo structure. manipulating their CrashpadInfo structure.
The two extensibility points are: The two extensibility points are:
@ -461,6 +463,18 @@ The two extensibility points are:
In both cases the CrashpadInfo structure has to be updated before a crash In both cases the CrashpadInfo structure has to be updated before a crash
occurs. occurs.
##### Embedder Extensibility
Additionally, embedders of the handler can provide "user stream data source"
instances to the handler's main function. Any time a minidump is written, these
instances get called.
Each data source may contribute a custom stream to the minidump, which can be
computed from e.g. system or application state relevant to the crash.
As a case in point, it can be handy to know whether the system was under memory
or other resource duress at the time of crash.
### Dependencies ### Dependencies
Aside from system headers and APIs, when used outside of Chromium, Crashpad has Aside from system headers and APIs, when used outside of Chromium, Crashpad has