-
Bug
-
Resolution: Fixed
-
P3
-
9
-
None
-
b02
-
generic
-
generic
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8045069 | 8u25 | Sundararajan Athijegannathan | P3 | Resolved | Fixed | b01 |
| JDK-8037986 | 8u20 | Sundararajan Athijegannathan | P3 | Resolved | Fixed | b09 |
| JDK-8052469 | emb-8u26 | Sundararajan Athijegannathan | P3 | Resolved | Fixed | b18 |
Error, TypeError etc. capture stack trace at the time of throwing the exception. This is inconsistent with Java as well as other js implementations like v8.
File: test.js
var e = new Error();
print("hello");
try {
throw e;
} catch (e) {
print(e.stack);
}
--- output --
hello
Error
at <program> (test.js:6)
-- expected --
hello
Error
at <program> (test.js:1)
File: test.js
var e = new Error();
print("hello");
try {
throw e;
} catch (e) {
print(e.stack);
}
--- output --
hello
Error
at <program> (test.js:6)
-- expected --
hello
Error
at <program> (test.js:1)
- backported by
-
JDK-8037986 Error objects should capture stack at the constructor
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
- relates to
-
JDK-8029967 Final steps to have Error compliant with V8 Error API
-
- Closed
-