IPC Fuzzer: Initialize mojo in the replay process.

IPC Fuzzer: Initialize mojo in the replay process.

Without this, ChannelMojo doesn't work.

R=inferno@chromium.org, tsepez@chromium.org
TBR=jamesr@chromium.org
BUG=453571
Committed: https://crrev.com/a89461fe15779ec8e939f2b16acd282155c42ab1
Cr-Commit-Position: refs/heads/master@{#314010}

[inferno, 2015-01-30 20:42:22]

https://codereview.chromium.org/867903006/diff/1/tools/ipc_fuzzer/replay/repl...
File tools/ipc_fuzzer/replay/replay_process.cc (right):

https://codereview.chromium.org/867903006/diff/1/tools/ipc_fuzzer/replay/repl...
tools/ipc_fuzzer/replay/replay_process.cc:25: void InitializeMojo() {
Why do we need to duplicate this. can we not call InitializeMojo
https://code.google.com/p/chromium/codesearch#chromium/src/content/app/mojo/m...

[Hajime Morrita, 2015-01-30 21:07:35]

On 2015/01/30 20:42:22, inferno wrote:
>
https://codereview.chromium.org/867903006/diff/1/tools/ipc_fuzzer/replay/repl...
> File tools/ipc_fuzzer/replay/replay_process.cc (right):
> 
>
https://codereview.chromium.org/867903006/diff/1/tools/ipc_fuzzer/replay/repl...
> tools/ipc_fuzzer/replay/replay_process.cc:25: void InitializeMojo() {
> Why do we need to duplicate this. can we not call InitializeMojo
>
https://code.google.com/p/chromium/codesearch#chromium/src/content/app/mojo/m...
Unfortunately it isn't a part of the public content API. I'd rather do it by
ourselves.

[Tom Sepez, 2015-01-30 21:15:52]

LGTM.  Note that another possiblity might be to make the replay process inherit
from content::ChildProcess and ChildThread so as to use the same code as the
real renderer.  I tried to cobble this together the other day, but lots of
things were missing ...

[inferno, 2015-01-30 21:31:08]

On 2015/01/30 21:07:35, morrita wrote:
> On 2015/01/30 20:42:22, inferno wrote:
> >
>
https://codereview.chromium.org/867903006/diff/1/tools/ipc_fuzzer/replay/repl...
> > File tools/ipc_fuzzer/replay/replay_process.cc (right):
> > 
> >
>
https://codereview.chromium.org/867903006/diff/1/tools/ipc_fuzzer/replay/repl...
> > tools/ipc_fuzzer/replay/replay_process.cc:25: void InitializeMojo() {
> > Why do we need to duplicate this. can we not call InitializeMojo
> >
>
https://code.google.com/p/chromium/codesearch#chromium/src/content/app/mojo/m...
> Unfortunately it isn't a part of the public content API. I'd rather do it by
> ourselves.

lgtm. please add a comment+todo on this.

[Hajime Morrita, 2015-01-30 21:37:53]

On 2015/01/30 21:31:08, inferno wrote:
> On 2015/01/30 21:07:35, morrita wrote:
> > On 2015/01/30 20:42:22, inferno wrote:
> > >
> >
>
https://codereview.chromium.org/867903006/diff/1/tools/ipc_fuzzer/replay/repl...
> > > File tools/ipc_fuzzer/replay/replay_process.cc (right):
> > > 
> > >
> >
>
https://codereview.chromium.org/867903006/diff/1/tools/ipc_fuzzer/replay/repl...
> > > tools/ipc_fuzzer/replay/replay_process.cc:25: void InitializeMojo() {
> > > Why do we need to duplicate this. can we not call InitializeMojo
> > >
> >
>
https://code.google.com/p/chromium/codesearch#chromium/src/content/app/mojo/m...
> > Unfortunately it isn't a part of the public content API. I'd rather do it by
> > ourselves.
> 
> lgtm. please add a comment+todo on this.
Done. Landing...

[Hajime Morrita, 2015-01-30 21:38:19]

The CQ bit was checked by morrita@chromium.org

[Hajime Morrita, 2015-01-30 21:39:04]

On 2015/01/30 21:15:52, Tom Sepez wrote:
> LGTM.  Note that another possiblity might be to make the replay process
inherit
> from content::ChildProcess and ChildThread so as to use the same code as the
> real renderer.  I tried to cobble this together the other day, but lots of
> things were missing ...
Agreed. Sharing more underlying bits will be good in general.

[commit-bot: I haz the power, 2015-01-30 21:39:55]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/867903006/20001

[commit-bot: I haz the power, 2015-01-30 21:46:30]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2015-01-30 21:46:31]

Try jobs failed on following builders:
  chromium_presubmit on tryserver.chromium.linux
(http://build.chromium.org/p/tryserver.chromium.linux/builders/chromium_presub...)

[Hajime Morrita, 2015-01-30 21:53:43]

The CQ bit was checked by morrita@chromium.org

[commit-bot: I haz the power, 2015-01-30 21:54:18]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/867903006/40001

[commit-bot: I haz the power, 2015-01-30 22:00:39]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2015-01-30 22:00:40]

Try jobs failed on following builders:
  chromium_presubmit on tryserver.chromium.linux
(http://build.chromium.org/p/tryserver.chromium.linux/builders/chromium_presub...)

[Hajime Morrita, 2015-01-30 22:03:00]

The CQ bit was checked by morrita@chromium.org

[commit-bot: I haz the power, 2015-01-30 22:03:37]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/867903006/40001

[commit-bot: I haz the power, 2015-01-30 22:37:14]

Committed patchset #3 (id:40001)

[commit-bot: I haz the power, 2015-01-30 22:38:17]

Patchset 3 (id:??) landed as
https://crrev.com/a89461fe15779ec8e939f2b16acd282155c42ab1
Cr-Commit-Position: refs/heads/master@{#314010}