* Electron version: 1.7.2
* Operating system: macOS 10.12.5

### Expected behavior

Forked processes can be started with `--inspect` or `--inspect-brk` for debugging them.

### Actual behavior

This option does not seem to have any impact.

### How to reproduce

* `git clone https://github.com/bpasero/electron-inspect.git`
* `npm install`
* `./node_modules/.bin/electron .`

=> we fork the process in https://github.com/bpasero/electron-inspect/blob/master/fork.js#L3
=> you see a file `tempXYZ` appearing which means `script.js` was executed
=> this is unexpected because `fork.js` was forked with `--inspect-brk`

atom/app/node_main.cc
#if defined(OS_WIN)
    process.SetMethod("log", &AtomBindings::Log);
#endif
    process.SetMethod("crash", &AtomBindings::Crash);
    
    auto reporter = mate::Dictionary::CreateEmpty(gin_env.isolate());
    reporter.SetMethod("start", &crash_reporter::CrashReporter::StartInstance);
    process.Set("crashReporter", reporter);
    node::LoadEnvironment(env);
    bool more;
    do {
      more = uv_run(env->event_loop(), UV_RUN_ONCE);
      if (more == false) {
        node::EmitBeforeExit(env);
        
        
        more = uv_loop_alive(env->event_loop());
        if (uv_run(env->event_loop(), UV_RUN_NOWAIT) != 0)
          more = true;
      }
    } while (more == true);
    exit_code = node::EmitExit(env);
    node::RunAtExit(env);
    node::FreeEnvironment(env);
  }
  v8::V8::Dispose();
  return exit_code;
}
}