Benedikt Meurer 40dd065823 [debugger] Properly deal with settled promises in catch prediction. ... The catch prediction logic got confused when we merged the reactions and result fields of JSPromise, because for settled promises it would start to treat the result as reactions list, leading to a crash most likely or memory corruption in the worst case (only if break on uncaught exception is enabled). We can only inspect reactions when the promise is still in "pending" state. Bug: chromium:808973, v8:7253 Change-Id: I15162c96fce959a052fbc628addd9418da39327c Reviewed-on: https://chromium-review.googlesource.com/903163 Reviewed-by: Jakob Gruber <jgruber@chromium.org> Commit-Queue: Benedikt Meurer <bmeurer@chromium.org> Cr-Commit-Position: refs/heads/master@{#51106}		2018-02-06 08:42:35 +00:00
..
bugs/harmony	[debug-wrapper] migrate some scope related tests	2016-12-14 07:20:33 +00:00
debug	Reland "Fix "this" value in lazily-parsed module functions."	2017-12-12 17:23:35 +00:00
protocol	[debugger] basic test infrastructure for new debugger test api.	2016-10-21 06:38:05 +00:00
regress	[debugger] Properly deal with settled promises in catch prediction.	2018-02-06 08:42:35 +00:00
wrapper	[debugger] Various break-related functionality in test wrapper	2016-10-28 08:18:34 +00:00
debugger.isolate	[build] Remove remaining disable-inspector options in GN	2017-04-05 17:59:07 +00:00
debugger.status	[heap] Minor MC: Pause concurrent marking	2017-12-08 13:33:33 +00:00
test-api.js	[debugger] removed BreakPositionAlignment.STATEMENT_ALIGNED	2017-06-20 15:01:47 +00:00
testcfg.py	[test] Remove context usage from test processors	2018-02-01 10:35:02 +00:00