Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Blocker
-
Resolution: Fixed
-
Affects Version/s: 2.9.0, 2.9.0.1, 2.9.1, 2.9.2
-
Fix Version/s: 2.9.3
-
Component/s: None
-
Labels:None
-
Number of attachments :
Description
Currently we always return true for java.lang.Class.desiredAssertionStatus and swallow -ea/-da/-esa/-dsa command line arguments. Some programs (the X10 compiler for one) fail assertions during their execution and therefore returning true causes these program to die with an AssertionError. We should implement this properly so that we are equivalent to a standard JVM.
This bug replaces bug 1147437 on sourceforge which has more details and poses the unanswered question as to whether we want to move from VM._assert to assert:
http://sourceforge.net/tracker/index.php?func=detail&aid=1147437&group_id=128805&atid=712768
Issue Links
| This issue is superceded by: | ||||
| RVM-317 | Integrate assertion support with Classpath |
|
|
|
Patch committed in r13822.