[wasm] Add test case for stack trace of wasm traps

[wasm] Add test case for stack trace of wasm traps

Since traps now throw real Error objects, we get stack traces
containing <WASM> functions on top-level. The additional tests check
for two traps: unreachable and memory out-of-bounds.

R=ahaas@chromium.org, jfb@chromium.org, titzer@chromium.org
BUG=

Committed: https://crrev.com/e530556471efd889494c4aaec1687adee52b0579
Cr-Commit-Position: refs/heads/master@{#35691}

[titzer, 2016-04-18 11:39:33]

lgtm

[Clemens Hammacher, 2016-04-21 09:07:26]

The CQ bit was checked by clemensh@chromium.org

[commit-bot: I haz the power, 2016-04-21 09:07:33]

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

[commit-bot: I haz the power, 2016-04-21 09:36:55]

Committed patchset #3 (id:40001)

[commit-bot: I haz the power, 2016-04-22 19:14:17]

Description was changed from

==========
[wasm] Add test case for stack trace of wasm traps

Since traps now throw real Error objects, we get stack traces
containing <WASM> functions on top-level. The additional tests check
for two traps: unreachable and memory out-of-bounds.

R=ahaas@chromium.org, jfb@chromium.org, titzer@chromium.org
BUG=
==========

to

==========
[wasm] Add test case for stack trace of wasm traps

Since traps now throw real Error objects, we get stack traces
containing <WASM> functions on top-level. The additional tests check
for two traps: unreachable and memory out-of-bounds.

R=ahaas@chromium.org, jfb@chromium.org, titzer@chromium.org
BUG=

Committed: https://crrev.com/e530556471efd889494c4aaec1687adee52b0579
Cr-Commit-Position: refs/heads/master@{#35691}
==========

[commit-bot: I haz the power, 2016-04-22 19:14:18]

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