-
Type:
Enhancement
-
Resolution: Fixed
-
Priority:
P3
-
Affects Version/s: 9
-
Component/s: hotspot
-
b45
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8083138 | emb-9 | Coleen Phillimore | P3 | Resolved | Fixed | team |
| JDK-8252308 | openjdk8u272 | Coleen Phillimore | P3 | Resolved | Fixed | b06 |
| JDK-8249444 | 8u271 | Coleen Phillimore | P3 | Resolved | Fixed | b02 |
| JDK-8251625 | emb-8u271 | Coleen Phillimore | P3 | Resolved | Fixed | team |
My reasoning is that since JFR events can trace exceptions and their stack traces with pretty low, near zero, overhead - can we do the same for -XX:+TraceExceptions and make it available in release builds? Frequently a debug build changes timings, so my original bug doesn't reproduce in fast debug.
It would be great to have.
It would be great to have.
- backported by
-
JDK-8083138 Need to enable -XX:+TraceExceptions in release builds
-
- Resolved
-
-
JDK-8249444 Need to enable -XX:+TraceExceptions in release builds
-
- Resolved
-
-
JDK-8251625 Need to enable -XX:+TraceExceptions in release builds
-
- Resolved
-
-
JDK-8252308 Need to enable -XX:+TraceExceptions in release builds
-
- Resolved
-