mash: Use shared memory to send crash keys to crash_reporter |
|||||
Issue descriptionChrome has a concept of "crash keys" which are pieces of metadata sent to the crash server when the browser crashes. They are written as part of in-process crash dumping. For mash we're using the system crash_reporter for crashes, so we're not in-process. We need a way to export a little bit of metadata. vapier suggested environment variables. Notes to self: * environment is in /proc/<pid>/environ * Record variables with setenv(), which allocates and copies strings on each call. * For efficiency we could preallocate string buffers, use putenv() to connect them to the env variables, then copy our data into the buffers.
,
Mar 7 2017
On hold. Not needed for Q1. Might be slightly easier after crash team finishes crash key registration refactor from issue 598854 (and need to be sure this approach works with their new plans).
,
Sep 25 2017
,
May 2 2018
Still on hold. We're using content-layer process launching for the foreseeable future, which allows us to use Chrome's crash reporter and crash keys. It's also possible Crashpad for Chrome OS will ship before mash, which might make this easier to handle.
,
Aug 14
We've switched back to Breakpad for mash. It looks like Crashpad for Chrome OS will happen before mash ships. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by jamescook@chromium.org
, Feb 18 2017