[wasm] Handle potentially null callee-pc

[wasm] Handle potentially null callee-pc

This only happens if there is a asm.js-wasm-frame on top of the stack
trace, which was not covered by our tests so far. The regression test
create a stack overflow in asm.js code, triggering this case.

R=mstarzinger@chromium.org
CC=titzer@chromium.org, bradnelson@chromium.org
BUG=chromium:673241
Committed: https://crrev.com/c69b48adc4cd4c36c44eac8efcac51bdbb1fdc5c
Cr-Commit-Position: refs/heads/master@{#41639}

[Clemens Hammacher, 2016-12-12 09:33:12]

The CQ bit was checked by clemensh@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-12-12 09:33:22]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-12-12 09:49:52]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-12-12 09:49:52]

Dry run: Try jobs failed on following builders:
  v8_linux64_asan_rel_ng on master.tryserver.v8 (JOB_FAILED,
http://build.chromium.org/p/tryserver.v8/builders/v8_linux64_asan_rel_ng/buil...)
  v8_linux64_asan_rel_ng_triggered on master.tryserver.v8 (JOB_FAILED,
http://build.chromium.org/p/tryserver.v8/builders/v8_linux64_asan_rel_ng_trig...)
  v8_win_nosnap_shared_rel_ng on master.tryserver.v8 (JOB_FAILED,
http://build.chromium.org/p/tryserver.v8/builders/v8_win_nosnap_shared_rel_ng...)
  v8_win_nosnap_shared_rel_ng_triggered on master.tryserver.v8 (JOB_FAILED,
http://build.chromium.org/p/tryserver.v8/builders/v8_win_nosnap_shared_rel_ng...)

[Clemens Hammacher, 2016-12-12 09:53:01]

The CQ bit was checked by clemensh@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-12-12 09:53:12]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[Michael Starzinger, 2016-12-12 09:53:54]

LGTM.

https://codereview.chromium.org/2562333002/diff/1/test/mjsunit/regress/regres...
File test/mjsunit/regress/regress-673241.js (right):

https://codereview.chromium.org/2562333002/diff/1/test/mjsunit/regress/regres...
test/mjsunit/regress/regress-673241.js:13: generateAsmJs()();
nit: Shouldn't this say "assertThrows(generateAsmJs(), RangeError)" here?

[Clemens Hammacher, 2016-12-12 09:57:05]

The CQ bit was checked by clemensh@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-12-12 09:57:12]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-12-12 10:11:40]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-12-12 10:11:41]

Dry run: Try jobs failed on following builders:
  v8_linux64_gyp_rel_ng on master.tryserver.v8 (JOB_FAILED,
http://build.chromium.org/p/tryserver.v8/builders/v8_linux64_gyp_rel_ng/build...)
  v8_linux64_gyp_rel_ng_triggered on master.tryserver.v8 (JOB_FAILED,
http://build.chromium.org/p/tryserver.v8/builders/v8_linux64_gyp_rel_ng_trigg...)

[Clemens Hammacher, 2016-12-12 12:04:31]

The CQ bit was checked by clemensh@chromium.org

[Clemens Hammacher, 2016-12-12 12:04:32]

The patchset sent to the CQ was uploaded after l-g-t-m from
mstarzinger@chromium.org
Link to the patchset: https://codereview.chromium.org/2562333002/#ps60001
(title: "Remove check for RangeError, becuase of unrelated bug")

[commit-bot: I haz the power, 2016-12-12 12:04:36]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-12-12 12:29:52]

CQ is committing da patch.

Bot data: {"patchset_id": 60001, "attempt_start_ts": 1481544271515990,
"parent_rev": "e89c823f9c9fb305ba1ec7c1643f41e022bb1bff", "commit_rev":
"c1aadf92b9a6916ca176053269ed7a4557660264"}

[commit-bot: I haz the power, 2016-12-12 12:29:55]

Description was changed from

==========
[wasm] Handle potentially null callee-pc

This only happens if there is a asm.js-wasm-frame on top of the stack
trace, which was not covered by our tests so far. The regression test
create a stack overflow in asm.js code, triggering this case.

R=mstarzinger@chromium.org
CC=titzer@chromium.org, bradnelson@chromium.org
BUG=chromium:673241
==========

to

==========
[wasm] Handle potentially null callee-pc

This only happens if there is a asm.js-wasm-frame on top of the stack
trace, which was not covered by our tests so far. The regression test
create a stack overflow in asm.js code, triggering this case.

R=mstarzinger@chromium.org
CC=titzer@chromium.org, bradnelson@chromium.org
BUG=chromium:673241

Review-Url: https://codereview.chromium.org/2562333002
==========

[commit-bot: I haz the power, 2016-12-12 12:29:55]

Committed patchset #4 (id:60001)

[commit-bot: I haz the power, 2016-12-12 12:30:47]

Description was changed from

==========
[wasm] Handle potentially null callee-pc

This only happens if there is a asm.js-wasm-frame on top of the stack
trace, which was not covered by our tests so far. The regression test
create a stack overflow in asm.js code, triggering this case.

R=mstarzinger@chromium.org
CC=titzer@chromium.org, bradnelson@chromium.org
BUG=chromium:673241

Review-Url: https://codereview.chromium.org/2562333002
==========

to

==========
[wasm] Handle potentially null callee-pc

This only happens if there is a asm.js-wasm-frame on top of the stack
trace, which was not covered by our tests so far. The regression test
create a stack overflow in asm.js code, triggering this case.

R=mstarzinger@chromium.org
CC=titzer@chromium.org, bradnelson@chromium.org
BUG=chromium:673241

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

[commit-bot: I haz the power, 2016-12-12 12:30:48]

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