[Bug 394] pre Epoch bug : java.lang.ExceptionInInitializerError on systems with uninitialized clock/triggered after Y2038 time overflow on 32bit systems

[bugzilla-daemon at icedtea.classpath.org]

http://icedtea.classpath.org/bugzilla/show_bug.cgi?id=394


xerxes at zafena.se changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Platform|32-bit                      |all
            Summary|Y2038 time overflow/pre     |pre Epoch bug :
                   |Epoch bug :                 |java.lang.ExceptionInInitial
                   |java.lang.ExceptionInInitial|izerError on systems with
                   |izerError on systems with   |uninitialized
                   |uninitialized clock         |clock/triggered after Y2038
                   |                            |time overflow on 32bit
                   |                            |systems




------- Comment #12 from xerxes at zafena.se  2010-06-26 21:50 -------

(In reply to comment #10)
> The Y2038 bug is an issue with 32-bit systems only as time_t = pointer size. 
> So it affects x86 and arm, but not x86_64 where time_t will be 64-bit.

This bug can still hit on both 64bit and 32bit systems since time_t are
*signed*.

when time_t < 0 then it refers to pre Epoch time on both 32bit and 64bit
systems 

John wrote:
>Any checks that are failing simply because currentTimeMillis() is negative are
>bugs in themselves IMO (unless they really mean to check that the system clock
>is later than 1970), and should be fixed separately if found.

I cant agree more, and this bug are one of these cases when Java fails to
launch because currentTimeMillis() returns a negative number.


-- 
Configure bugmail: http://icedtea.classpath.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.