Simon Zünd 0625c06610 [inspector] Check for null pointer after creating a stack trace ... 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}		2020-11-13 07:37:13 +00:00
..
regress-crbug-1147552-expected.txt	[inspector] Check for null pointer after creating a stack trace	2020-11-13 07:37:13 +00:00
regress-crbug-1147552.js	[inspector] Check for null pointer after creating a stack trace	2020-11-13 07:37:13 +00:00