diff options
| author | agl@chromium.org <agl@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-06-23 18:29:11 +0000 |
|---|---|---|
| committer | agl@chromium.org <agl@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-06-23 18:29:11 +0000 |
| commit | ee052b86770a2d1d269502dd6c903276024e7826 (patch) | |
| tree | e01b2e23116a733fb7b95130ae74b1abc60e6e84 /chrome/app/breakpad_linux.cc | |
| parent | 3ae83989fbb4bc835109d709c4e71650f0788a14 (diff) | |
| download | chromium_src-ee052b86770a2d1d269502dd6c903276024e7826.zip chromium_src-ee052b86770a2d1d269502dd6c903276024e7826.tar.gz chromium_src-ee052b86770a2d1d269502dd6c903276024e7826.tar.bz2 | |
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
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@19035 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/app/breakpad_linux.cc')
| -rw-r--r-- | chrome/app/breakpad_linux.cc | 6 |
1 files changed, 4 insertions, 2 deletions
diff --git a/chrome/app/breakpad_linux.cc b/chrome/app/breakpad_linux.cc index 2b293be..588118a 100644 --- a/chrome/app/breakpad_linux.cc +++ b/chrome/app/breakpad_linux.cc @@ -518,8 +518,10 @@ void InitCrashReporter() { const CommandLine& parsed_command_line = *CommandLine::ForCurrentProcess(); const std::wstring process_type = parsed_command_line.GetSwitchValue(switches::kProcessType); - if (process_type.empty()) + if (process_type.empty()) { EnableCrashDumping(); - else if (process_type == switches::kRendererProcess) + } else if (process_type == switches::kRendererProcess || + process_type == switches::kZygoteProcess) { EnableRendererCrashDumping(); + } } |