[wasm] Add a cctest for the stack on a wasm trap

[wasm] Add a cctest for the stack on a wasm trap

In contrast to the existing cctest, this time the error is not thrown
from javascript, but by a trap in wasm. And in contrast to the mjsunit
tests, this checks the detailed stack trace, not the simple one.

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

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

[Clemens Hammacher, 2016-04-12 14:58:20]

Oh damn, looks like I need to rebase...

[Clemens Hammacher, 2016-04-12 15:56:37]

On 2016/04/12 at 14:58:20, Clemens Hammacher wrote:
> Oh damn, looks like I need to rebase...

OK, much greener now :)

[JF, 2016-04-12 19:38:54]

lgtm

https://codereview.chromium.org/1884593002/diff/20001/test/cctest/wasm/wasm-r...
File test/cctest/wasm/wasm-run-utils.h (right):

https://codereview.chromium.org/1884593002/diff/20001/test/cctest/wasm/wasm-r...
test/cctest/wasm/wasm-run-utils.h:414: const char* debug_name = "wasm_unnamed")
It's probably clearer to give it a name with unusual characters, like "WASM
UNNAMED>".

[Clemens Hammacher, 2016-04-13 07:45:18]

https://codereview.chromium.org/1884593002/diff/20001/test/cctest/wasm/wasm-r...
File test/cctest/wasm/wasm-run-utils.h (right):

https://codereview.chromium.org/1884593002/diff/20001/test/cctest/wasm/wasm-r...
test/cctest/wasm/wasm-run-utils.h:414: const char* debug_name = "wasm_unnamed")
On 2016/04/12 at 19:38:54, JF wrote:
> It's probably clearer to give it a name with unusual characters, like "WASM
UNNAMED>".

Done.

[titzer, 2016-04-18 10:41:11]

lgtm

[Clemens Hammacher, 2016-04-20 14:53:09]

The CQ bit was checked by clemensh@chromium.org

[Clemens Hammacher, 2016-04-20 14:53:10]

The patchset sent to the CQ was uploaded after l-g-t-m from jfb@chromium.org,
titzer@chromium.org
Link to the patchset: https://codereview.chromium.org/1884593002/#ps80001
(title: "one more c++ style fix")

[commit-bot: I haz the power, 2016-04-20 14:53:12]

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

[commit-bot: I haz the power, 2016-04-20 15:09:41]

Committed patchset #5 (id:80001)

[nodir1, 2016-04-22 18:44:24]

Description was changed from

==========
[wasm] Add a cctest for the stack on a wasm trap

In contrast to the existing cctest, this time the error is not thrown
from javascript, but by a trap in wasm. And in contrast to the mjsunit
tests, this checks the detailed stack trace, not the simple one.

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

to

==========
[wasm] Add a cctest for the stack on a wasm trap

In contrast to the existing cctest, this time the error is not thrown
from javascript, but by a trap in wasm. And in contrast to the mjsunit
tests, this checks the detailed stack trace, not the simple one.

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

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

[nodir1, 2016-04-22 18:44:25]

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