Boiledbeans

Drama! Intrigue! Geekiness!

February 12, 2012

And you said it was bad?

devadutta @ 11:59 pm, GMT +0000 ( 1329091181 ) Play

Sitter of all sitters. Identify the “problem”.

Cracked by: Sumanth Patlolla , rickde , Manish Achuth , finkle , shrik , rohanquizzer , Rogi , Vishwas B Sharma , KK , Godzilla101 , Ananth , raklodramA , Raghuvansh , jowens , badideabear , Bharath , Dibyo , Jayaprakash B R , , debjani , Anjul , Rahulk and anurag

Answer:
Quoting badideabear
Y2K38 problem. affects computers that store dates in 32-bit form because after 03:14:07 UTC on Tuesday, 19 January 2038, the number of bits needed to express the date will exceed 32.

Points assigned by AutoRaja. Review by lazy humans pending.

25 Responses to “And you said it was bad?”

  1. Sumanth Patlolla
    27
    8
    7

    Y2K38 Problem :)


  2. rickde
    4
    3
    3

    Year 2038 problem


  3. Manish Achuth
    16
    9
    8

    Year 2038 problem.


  4. finkle

    Integer overflow in time counters, aka y2k bug aka y2k38 bug


  5. shrik
    10
    7
    9

    The year 2038 problem, also known as the Unix Millennium Bug.


  6. The Year 2038 aka Y2K28 problem


  7. Rogi
    48
    10
    5

    The Uxix year 2038 problem.


  8. Unix Millenium Bug – Y2K38 Problem. The epoch variable time_t is a signed integer and hence when it outruns the binary of signed integer it resets to 1901.


  9. KK
    1
    4
    5

    Year 2038 problem


  10. Godzilla101

    y2k37


  11. Ananth
    4
    5
    9

    Year 2038 problem


  12. The year 2038 problem (also known as the Unix Millennium Bug[citation needed], Y2K38 or Y2.038K


  13. Raghuvansh
    1
    9
    4

    The Unix Year 2038 problem.


  14. jowens
    13
    2

    Year 2038 problem (32-bit Unix time overflows)


  15. badideabear
    5
    1
    1

    Y2K38 problem. affects computers that store dates in 32-bit form because after 03:14:07 UTC on Tuesday, 19 January 2038, the number of bits needed to express the date will exceed 32.


  16. Bharath
    4
    2
    4

    Year 2038 problem


  17. Dibyo
    11
    14
    10

    year 2038 problem


  18. Year 2038 problem / Unix Millenium Bug


  19. Anonymous

    year 2038 time bug


  20. debjani

    year 2038 bug


  21. Anjul
    2
    1
    1

    Unix Millennium Bug


  22. Rahulk
    2
    5

    The year 2038 problem (also known as the Unix Millennium Bug), Y2K38 or Y2.038K


  23. Gostei muito desse site!


  24. anurag

    year 2038 problem when the 32bit integer used to represent UTC overflows.


  25. thanks for share!


« Previous « Aqua Awesomea « | » Not the Dark Side » Next »