JDK-4791717 : need SuppressErrorAt option to enable testing past irrelevant asserts
  • Type: Bug
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 1.4.2
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • OS: generic
  • CPU: sparc
  • Submitted: 2002-12-10
  • Updated: 2012-10-08
  • Resolved: 2002-12-17
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other
1.4.2 b11Fixed
Related Reports
Relates :  
JDK-6618726 - Introduce -XX:+UnlockExperimentalVMOptions flag
Description
When testing applications with fastdebug builds, it often happens
that an assertion is hit which terminates the VM, even though the
assertion is regarded as benign by the customer.  This can make it
difficult to diagnose the root cause of application failure, since
it becomes impossible to run the fastdebug build up to the point
of failure where (we hope) a relevant assertion will trip.
Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: mantis-beta FIXED IN: mantis-beta INTEGRATED IN: mantis-b11 mantis-beta
14-06-2004
EVALUATION See suggested fix.
11-06-2004
SUGGESTED FIX Create an option -XX:SuppressErrorAt=file:line,file:line... . When the VM throws an assertion, it should print a message suggesting such an option, in case the user wishes to proceed past the assertion.
11-06-2004