On Apr 2, 11:12 am, Marshall Greenblatt <magreenbl...@gmail.com>
wrote:
> Hi All,
>
> Is there a current document that explains the multi-process crash
> service/reporting design used by Chrome via crash_service? I see the
> documents available athttp://code.google.com/p/google-breakpad/w/listbut
> they appear a bit dated.
You found the right document and but you are correct, it does not
reflect the out-of-process crash generation enhancements.
Let me ping the developer responsible for a document update.
>
> Thanks,
> Marshall
In a nutshell, the idea is that there is a long lived process that is
responsible for creating the crash dumps (crash_service) and clients
register to it via a named pipe transaction. In the registration, the
client gives its own process handle and the crash_server returns two
events. When the client crashes, it signals one event and waits (on
the other) for the server to wake up and take the dump. The dump
capture is straightforward because the windows apis already support
cross process dump capture.
The core idea is to minimize the code that is run on the client once a
fatal exception is in play. Also sandboxed processes would need more
permissions than desired if they were to create their own dumps.
--~--~---------~--~----~------------~-------~--~----~
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
-~----------~----~----~----~------~----~------~--~---
