[test] add tests for async function stacktraces

[test] add tests for async function stacktraces

BUG=v8:4483
R=littledan@chromium.org

Committed: https://crrev.com/02f228eccdfcfab4081c2494ade52e54702b692c
Cr-Commit-Position: refs/heads/master@{#36365}

[caitp (gmail), 2016-05-18 22:36:15]

stacktrace tests, revealing some bizarre FNI behaviours that I hope we can fix.
Not having async stacktraces in v8 is a bit unfortunate as well, but maybe it's
fine to let Chromium implement these.

[Dan Ehrenberg, 2016-05-18 23:58:53]

lgtm

These look like some good tests (to your comments, those cases actually seem
fine to me).

Future test ideas: Do async stack traces give us any extra behavior (e.g., as
tested by some of the things in test/mjsunit/harmony), or do we always get good
stacks "for free" because it's all based on generators? Is there anything else
you might test about how async stacks, e.g., from explicit use of
Promise.prototype.then, interacts with async functions, or that the debug events
are good? How about the interaction of async functions with the promise uncaught
rejection handler?

[Dan Ehrenberg, 2016-05-19 13:13:05]

The CQ bit was checked by littledan@chromium.org

[commit-bot: I haz the power, 2016-05-19 13:13:12]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1995723004/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1995723004/1

[commit-bot: I haz the power, 2016-05-19 13:27:39]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-05-19 13:30:07]

Description was changed from

==========
[test] add tests for async function stacktraces

BUG=v8:4483
R=littledan@chromium.org
==========

to

==========
[test] add tests for async function stacktraces

BUG=v8:4483
R=littledan@chromium.org

Committed: https://crrev.com/02f228eccdfcfab4081c2494ade52e54702b692c
Cr-Commit-Position: refs/heads/master@{#36365}
==========

[commit-bot: I haz the power, 2016-05-19 13:30:08]

Patchset 1 (id:??) landed as
https://crrev.com/02f228eccdfcfab4081c2494ade52e54702b692c
Cr-Commit-Position: refs/heads/master@{#36365}

[Michael Achenbach, 2016-05-19 14:50:56]

A revert of this CL (patchset #1 id:1) has been created in
https://codereview.chromium.org/1997453004/ by machenbach@chromium.org.

The reason for reverting is: Breaks gc stress:
https://build.chromium.org/p/client.v8/builders/V8%20Linux%20-%20gc%20stress/....