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

1. Sumanth Patlolla Says:
   February 18th, 2012 at 2:29 am, GMT +0000 ( 1329532169 )

   Y2K38 Problem :)

   
   
2. rickde Says:
   February 18th, 2012 at 3:50 am, GMT +0000 ( 1329537053 )

   Year 2038 problem

   X 15
   
   
3. Manish Achuth Says:
   February 18th, 2012 at 4:20 am, GMT +0000 ( 1329538808 )

   Year 2038 problem.

   
   
4. finkle Says:
   February 18th, 2012 at 8:33 am, GMT +0000 ( 1329553988 )

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

   
   
5. shrik Says:
   February 18th, 2012 at 7:33 pm, GMT +0000 ( 1329593590 )

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

   X 1
   
   
6. rohanquizzer Says:
   February 18th, 2012 at 8:56 pm, GMT +0000 ( 1329598561 )

   The Year 2038 aka Y2K28 problem

   
   
7. Rogi Says:
   February 19th, 2012 at 12:54 am, GMT +0000 ( 1329612856 )

   The Uxix year 2038 problem.

   
   
8. Vishwas B Sharma Says:
   February 19th, 2012 at 5:53 am, GMT +0000 ( 1329630826 )

   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 Says:
   February 19th, 2012 at 6:08 am, GMT +0000 ( 1329631687 )

   Year 2038 problem

   X 7
   
   
10. Godzilla101 Says:
    February 19th, 2012 at 10:25 am, GMT +0000 ( 1329647104 )

    y2k37

    
    
11. Ananth Says:
    February 19th, 2012 at 7:03 pm, GMT +0000 ( 1329678181 )

    Year 2038 problem

    X 7
    
    
12. raklodramA Says:
    February 19th, 2012 at 9:08 pm, GMT +0000 ( 1329685730 )

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

    X 1
    
    
13. Raghuvansh Says:
    February 19th, 2012 at 9:10 pm, GMT +0000 ( 1329685808 )

    The Unix Year 2038 problem.

    
    
14. jowens Says:
    February 19th, 2012 at 9:23 pm, GMT +0000 ( 1329686603 )

    Year 2038 problem (32-bit Unix time overflows)

    
    
15. badideabear Says:
    February 19th, 2012 at 9:24 pm, GMT +0000 ( 1329686687 )

    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 Says:
    February 20th, 2012 at 1:41 pm, GMT +0000 ( 1329745297 )

    Year 2038 problem

    
    
17. Dibyo Says:
    February 20th, 2012 at 6:39 pm, GMT +0000 ( 1329763150 )

    year 2038 problem

    
    
18. Jayaprakash B R Says:
    February 20th, 2012 at 8:48 pm, GMT +0000 ( 1329770892 )

    Year 2038 problem / Unix Millenium Bug

    
    
19. Anonymous Says:
    February 20th, 2012 at 9:51 pm, GMT +0000 ( 1329774675 )

    year 2038 time bug

    X 74
    
    
20. debjani Says:
    February 20th, 2012 at 9:51 pm, GMT +0000 ( 1329774702 )

    year 2038 bug

    
    
21. Anjul Says:
    February 21st, 2012 at 4:59 pm, GMT +0000 ( 1329843585 )

    Unix Millennium Bug

    
    
22. Rahulk Says:
    February 22nd, 2012 at 6:10 am, GMT +0000 ( 1329891047 )

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

    
    
23. Adriana Says:
    February 23rd, 2012 at 1:56 pm, GMT +0000 ( 1330005373 )

    Gostei muito desse site! Blame AutoRaja

    
    
24. anurag Says:
    February 23rd, 2012 at 10:02 pm, GMT +0000 ( 1330034539 )

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

    
    
25. Adriana Says:
    February 24th, 2012 at 4:52 pm, GMT +0000 ( 1330102344 )

    thanks for share! Blame AutoRaja