0625c06610
Currently, we assume that stack trace creation always succeeds while filling in the `exceptionDetails` structure. Stack trace creation can fail under some circumstances so this CL introduces a null check. R=clemensb@chromium.org Bug: chromium:1147552 Change-Id: I4055d5276bbb7bf178b648bfc7bd84a288626c09 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2532310 Commit-Queue: Simon Zünd <szuend@chromium.org> Reviewed-by: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#71169}
17 lines
605 B
JavaScript
17 lines
605 B
JavaScript
// Copyright 2020 the V8 project authors. All rights reserved.
|
|
// Use of this source code is governed by a BSD-style license that can be
|
|
// found in the LICENSE file.
|
|
|
|
const {session, Protocol} = InspectorTest.start('Regression test for crbug.com/1147552. Found by Clusterfuzz.');
|
|
|
|
Protocol.Runtime.enable();
|
|
|
|
Protocol.Runtime.setAsyncCallStackDepth({maxDepth: 10});
|
|
(async function test() {
|
|
await Protocol.Runtime.setMaxCallStackSizeToCapture({size: 0});
|
|
await Protocol.Runtime.evaluate({ expression: 'foo'});
|
|
|
|
InspectorTest.log('Test must not have crashed.')
|
|
InspectorTest.completeTest();
|
|
})();
|