NaCl: Don't pass the NaCl process's Windows handle to the renderer process

NaCl: Don't pass the NaCl process's Windows handle to the renderer process

The process handle is not used since we switched NaCl to using
Chromium's BrokerDuplicateHandle() function.

I have changed NaCl's SelLdrLauncher to not use the process ID or
process handle in this context, so returning dummy values of 0 and -1
will be OK: they will not get passed to kill(), waitpid() or
TerminateProcess().

BUG=http://code.google.com/p/nativeclient/issues/detail?id=2719
TEST=nacl_integration etc.


Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=133523

[jschuh, 2012-04-23 16:45:12]

On 2012/04/23 15:31:00, Mark Seaborn wrote:

lgtm

[sehr (please use chromium), 2012-04-23 18:32:05]

lgtm

[commit-bot: I haz the power, 2012-04-23 20:02:31]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/mseaborn@chromium.org/10134029/8001

[Mark Seaborn, 2012-04-23 20:04:15]

http://codereview.chromium.org/10134029/diff/8001/chrome/renderer/chrome_ppap...
File chrome/renderer/chrome_ppapi_interfaces.cc (right):

http://codereview.chromium.org/10134029/diff/8001/chrome/renderer/chrome_ppap...
chrome/renderer/chrome_ppapi_interfaces.cc:62: (base::ProcessHandle) -1;
As I discussed with David, I had to change this to a C-style cast to make it
compile on Linux and Windows, since neither static_cast and reinterpret_cast
work for converting an int to both an int (Unix) and a void* (Windows).

[commit-bot: I haz the power, 2012-04-23 21:34:16]

Change committed as 133523