Comment #6 on issue 27218 by [email protected]: [meta] Port the
windows chromium sandbox to 64 bits
http://code.google.com/p/chromium/issues/detail?id=27218
The following revision refers to this bug:
http://src.chromium.org/viewvc/chrome?view=rev&revision=36469
------------------------------------------------------------------------
r36469 | [email protected] | 2010-01-17 02:18:53 -0800 (Sun, 17 Jan 2010)
| 5 lines
Changed paths:
M
http://src.chromium.org/viewvc/chrome/trunk/src/sandbox/sandbox.gyp?r1=36469&r2=36468
M
http://src.chromium.org/viewvc/chrome/trunk/src/sandbox/src/sandbox.cc?r1=36469&r2=36468
M
http://src.chromium.org/viewvc/chrome/trunk/src/sandbox/src/sandbox_policy_base.cc?r1=36469&r2=36468
M
http://src.chromium.org/viewvc/chrome/trunk/src/sandbox/src/target_process.cc?r1=36469&r2=36468
Prepare the sandbox for integration with NaCl broker for 64-bit Windows.
The broker currently launches with --no-sandbox, so the 64-bit version of
the sandbox library is there only to allow successful build.
BUG=27218
TEST=none
Review URL: http://codereview.chromium.org/543058
------------------------------------------------------------------------
--
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
