[bugs #9495] GregorianCalendar.getTimeInMillis() fails with large millisecond values

[Stephen Crawley]

This mail is an automated notification from the bugs tracker
 of the project: classpath.




/**************************************************************************/
[bugs #9495] Full Item Snapshot:

URL: <http://savannah.gnu.org/bugs/?func=detailitem&item_id=9495>
Project: classpath
Submitted by: Stephen Crawley
On: Tue 06/29/2004 at 14:50

Severity:  5 - Average
Resolution:  None
Assigned to:  None
Status:  Open
Platform Version:  None


Summary:  GregorianCalendar.getTimeInMillis() fails with large millisecond 
values

Original Submission:  getTimeInMillis() converts large (magnitude) values to
year/month/day incorrectly.  Typically, it miscalculates
the month as negative and throws IllegalArgumentException.
For example:

FAIL: gnu.testlet.java.util.GregorianCalendar.conversion: uncaught exception at 
"Testing setTimeInMillis(281474976710656) i = 48" number 3
java.lang.IllegalArgumentException: month out of range
   at java.util.SimpleTimeZone.getOffset (SimpleTimeZone.java:684)
   at java.util.GregorianCalendar.computeFields (GregorianCalendar.java:610)
   at java.util.Calendar.setTimeInMillis (Calendar.java:541)
   at gnu.testlet.java.util.GregorianCalendar.conversion.testMonotonic1 
(conversion.java:79)
   at gnu.testlet.java.util.GregorianCalendar.conversion.test 
(conversion.java:41)
   at gnu.testlet.SimpleTestHarness.runtest (SimpleTestHarness.java:254)
   at gnu.testlet.SimpleTestHarness.main (SimpleTestHarness.java:364)

The problem is that GregorianCalendar is doing some key
conversion calculations using 'int' instead of 'long', and
intermediate values are overflowing.












For detailed info, follow this link:
<http://savannah.gnu.org/bugs/?func=detailitem&item_id=9495>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/