Comment #2 on issue 14969 by [email protected]: Zygote mode broke
crash reporting
http://code.google.com/p/chromium/issues/detail?id=14969
The following revision refers to this bug:
http://src.chromium.org/viewvc/chrome?view=rev&revision=19035
------------------------------------------------------------------------
r19035 | [email protected] | 2009-06-23 11:29:11 -0700 (Tue, 23 Jun 2009) |
15 lines
Changed paths:
M
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/app/breakpad_linux.cc?r1=19035&r2=19034
M
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/app/chrome_dll_main.cc?r1=19035&r2=19034
M
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/browser_main.cc?r1=19035&r2=19034
M
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/renderer/renderer_main.cc?r1=19035&r2=19034
Linux: fix crash reporting for zygote model
Crash reporting broke on Linux when we enabled the zygote model a
couple of weeks ago.
We can't just add "zygote" to the check for the process type because
the crash signal fd is set at the same time and that will change when
a renderer is forked from the zygote.
This fixes it for now, but it will need to be redone when we enable
sandboxing.
http://codereview.chromium.org/147004
BUG=14969
------------------------------------------------------------------------
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--~--~---------~--~----~------------~-------~--~----~
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
-~----------~----~----~----~------~----~------~--~---
