Another case of access to .stack. Maybe this can be mocked out?

The following revision refers to this bug:
  https://chromium.googlesource.com/v8/v8.git/+/09163d71bd3e1074dfa8ed439c789b67ee797133

commit 09163d71bd3e1074dfa8ed439c789b67ee797133
Author: machenbach <machenbach@chromium.org>
Date: Tue Jan 24 08:18:02 2017

[foozzie] Mock out stack traces

BUG= chromium:683494 
NOTRY=true
TBR=yangguo@chromium.org, jarin@chromium.org

Review-Url: https://codereview.chromium.org/2651713005
Cr-Commit-Position: refs/heads/master@{#42619}

[modify] https://crrev.com/09163d71bd3e1074dfa8ed439c789b67ee797133/tools/foozzie/v8_mock.js

ClusterFuzz has detected this issue as fixed in range 42618:42619.

Detailed report: https://cluster-fuzz.appspot.com/testcase?key=6052544758677504

Fuzzer: foozzie_js_mutation
Job Type: foozzie_ignition_staging
Platform Id: linux

Crash Type: V8 correctness failure
Crash Address: 
Crash State:
  configs: x64,fullcode:x64,ignition_staging
  sources: a8a
  
Sanitizer: address (ASAN)

Regressed: V8: 42370:42371
Fixed: V8: 42618:42619

Minimized Testcase (8.37 Kb): https://cluster-fuzz.appspot.com/download/AMIfv95KX5MbyIrjkt26bIY8e--lat12BGc51rXo0MY_Eod650jHONqKsq0u_RXtYx-cukEZTBNlfCnOWV9Xa98sPovKw9GpTEo1BOaWSx-RFVeJZ3FCC7czp6btBLX-hJTP0xzSjOSqP3Wv8Rsi-u_X4rEZGi-OV9xtKcySkPF2mIFacxW_XgLbCs5oYsnLyKEK2tSND38rj6YrI3_e31pEmTUvFOB92zHOYS3EgaK7iKFbj7nGxWnatX3B5VTtZgUaWKJGyevXgfPtKURvypEkDpY2GRODRAWuP0rEDds_9zl0deD2Aw4_MNWqulpOtkH9SHK3YVl7FT5lq2C5_3TluklxQzUu6n4mJVc0xzlcoL2aX9vG4s8?testcase_id=6052544758677504

See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.

ClusterFuzz testcase 6052544758677504 is verified as fixed, so closing issue.

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.