| Microsoft fixes coding gaffe 0xB16B00B5
|
engine
msg:4478181 | 2:31 pm on Jul 23, 2012 (gmt 0) |
Microsoft fixes coding gaffe 0xB16B00B5 [bbc.co.uk] Microsoft has swiftly fixed an embarrassing gaffe which saw a chunk of code labelled "big boobs".
The hexadecimal string 0xB16B00B5 was discovered lurking in code that helps a Microsoft program work with Linux open source software.
The controversial string came to light on a mailing list for developers who oversee the core, or kernel, of Linux.
The string was used every time the Microsoft program ran a virtual version of Linux.
|
|
|
incrediBILL
msg:4478303 | 11:23 pm on Jul 23, 2012 (gmt 0) |
Yeah, wouldn't want to offend the itty bitty... never mind, have their own committee and can deal with it.
What a waste of time.
|
brotherhood of LAN
msg:4478304 | 11:47 pm on Jul 23, 2012 (gmt 0) |
I've been guilty of that. When there's a bit of code that doesnt work as intended... that's taken hours of time to figure out and gets put into a separate file with a 'special' filename.
|
incrediBILL
msg:4478317 | 12:40 am on Jul 24, 2012 (gmt 0) |
I was bored once and put an error message where no error should ever occur, curious to see if it would ever occur, and made it just nutty enough that I was sure engineering would hear about it if it happened.
Three years later a hardware fault triggered the impossible in a newly installed customers system:
Another one bites the dust >CLAP!<
Another one bites the dust >CLAP!<
Program fall down and go BOOM! in line #245 |
|
Neither the customer, tech support nor the salesman were amused at the time but did chuckle about it over a beer later.
HOWEVER, there was a HUGE upside. Since the impossible message got displayed we knew it was something serious real quick and it probably saved us a ton of time figuring out the problem versus trying to track it down via the normal error traps typically displayed. Turns out the CPU was actually overheating because someone had blocked the ventilation and the computer was roasting itself.
|
|
|
