From: "MartinBosslet (Martin Bosslet)" Date: 2012-06-12T09:12:57+09:00 Subject: [ruby-core:45576] [ruby-trunk - Bug #6571] Time.mktime Y2K38 problem on 1.9.3p125 i386-mingw32 Issue #6571 has been updated by MartinBosslet (Martin Bosslet). Category changed from core to ext Thanks for your analysis, guys. Makes sense now, why I couldn't reproduce it on 64 bits. The original #6122 did not contain the actual error that was raised, so thanks Heesob for pointing me towards the solution! ---------------------------------------- Bug #6571: Time.mktime Y2K38 problem on 1.9.3p125 i386-mingw32 https://bugs.ruby-lang.org/issues/6571#change-27173 Author: MartinBosslet (Martin Bosslet) Status: Assigned Priority: Normal Assignee: MartinBosslet (Martin Bosslet) Category: ext Target version: 2.0.0 ruby -v: ruby 1.9.3p125 (2012-02-16) [i386-mingw32] =begin This came up in https://bugs.ruby-lang.org/issues/6122. (({Time.mktime(2038, 1, 19, 11, 14, 8)})) failed. To my understanding, 32 bit Time issues shouldn't occur in 1.9.3? I'm assigning this to Luis, maybe he knows about this and what to do? Please feel free to reassign back to me. =end -- http://bugs.ruby-lang.org/