deps: cherry-pick 989d7b9 from upstream V8

[targos]

Original commit message:

[error] Lazy stack trace formatting for Error.captureStackTrace

This reinstates the old behavior of Error.captureStackTrace prior to
4feafee9d9.  Like the builtin Error constructors, captureStackTrace now formats
the stack trace lazily once it is accessed.

Bug: v8:5962
Change-Id: I03821b73d26b7b40809a1fea98f9c820bfa05d6b
Reviewed-on: https://chromium-review.googlesource.com/574530
Reviewed-by: Camillo Bruni <cbruni@chromium.org>
Commit-Queue: Jakob Gruber <jgruber@chromium.org>
Cr-Commit-Position: refs/heads/master@{#46727}

Fixes: #13048
Fixes: #11343

/cc @nodejs/v8

Checklist

• make -j4 test (UNIX), or vcbuild test (Windows) passes
• commit message follows commit guidelines

Affected core subsystem(s)

V8

[MikeRalphson]

Many thanks @targos ! I believe this will also fix #11343

Also - did any of the performance test-suite show an improvement with this commit? Otherwise we would seem to have an area which is not covered in case of future regressions. Happy to submit a PR.

[targos]

Thank you, that's correct. I updated the message.

CI: https://ci.nodejs.org/job/node-test-pull-request/10051/
V8 CI: https://ci.nodejs.org/job/node-test-commit-v8-linux/901/

Edit: rebuild on OSX (green): https://ci.nodejs.org/job/node-test-commit-osx/12340/

[targos]

There is something wrong with the PPC machines:

Fetching V8 from chromium.googlesource.com
Error: Command 'download_from_google_storage --no_resume --platform=linux* --no_auth --bucket chromium-clang-format -s v8/buildtools/linux64/clang-format.sha1' returned non-zero exit status 1 in /home/iojs/build/workspace/node-test-commit-v8-linux/nodes/ppcbe-ubuntu1404/v8test/v8test/deps

[jasnell]

@targos ... can you rebase this?

[targos]

This commit is already present in V8 6.1. We can close this.