Properly reset external catcher if exception couldn't be externally caught.
authorager@chromium.org <ager@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Wed, 23 Feb 2011 06:55:47 +0000 (06:55 +0000)
committerager@chromium.org <ager@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Wed, 23 Feb 2011 06:55:47 +0000 (06:55 +0000)
commitae328e61b08ffc2f7d8d28d2459e3b0928a38124
tree806c2743a9c1e70ff5dee473e5d15aff0c310f11
parent3ff7aa0ea98bd2a9dca97d7faf4685ac709774ef
Properly reset external catcher if exception couldn't be externally caught.

We can wrongly assume that exception which is not intended to be caught
by external try/catch should be caught if this exception inherits
external catcher from some previous exception.  To prevent that,
clear external catcher when processing exceptions which cannot be
externally caught.

BUG=v8:1184
TEST=test/mjsunit/regress/regress-1184.js

Review URL: http://codereview.chromium.org/6538081

git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@6905 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
src/top.cc
test/mjsunit/regress/regress-1184.js [new file with mode: 0644]