Roll the revision of the seccomp sandbox forward. In the process, we also
fixed a missing include file in the zygote, that effectively disabled the
entire sandbox. This apparently happened recently, when the zygote code was
refactored.
BUG=n/a
TEST=SECCOMP_SANDBOX_DEBUGGING=1 ./out/Debug/chrome --enable-seccomp-sandbox, then verify that the sandbox is actually activated; it should be printing log data to the console
Review URL: https://chromiumcodereview.appspot.com/10407036
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@138521 0039d316-1c4b-4281-b951-d872f2087c98
diff --git a/DEPS b/DEPS
index da32a01..01c8d25 100644
--- a/DEPS
+++ b/DEPS
@@ -77,7 +77,7 @@
(Var("googlecode_url") % "google-url") + "/trunk@175",
"src/seccompsandbox":
- (Var("googlecode_url") % "seccompsandbox") + "/trunk@178",
+ (Var("googlecode_url") % "seccompsandbox") + "/trunk@186",
"src/sdch/open-vcdiff":
(Var("googlecode_url") % "open-vcdiff") + "/trunk@42",
