Follow Slashdot blog updates by subscribing to our blog RSS feed

 



Forgot your password?
typodupeerror

Slashdot videos: Now with more Slashdot!

  • View

  • Discuss

  • Share

We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).

×
Programming

+ - Whose bug is this anyway?->

Submitted by Anonymous Coward
An anonymous reader writes "Patrick Wyatt, one of the developers behind the original Warcraft and StarCraft games, has a post about some of the bug hunting he's done throughout his career. He covers familiar topics: crunch time leading to stupid mistakes, bugs in compilers rather than game code, and shares a story about finding a way to diagnose hardware failure for players of Guild Wars. Quoting: '[Mike O'Brien] wrote a module (“OsStress”) which would allocate a block of memory, perform calculations in that memory block, and then compare the results of the calculation to a table of known answers. He encoded this stress-test into the main game loop so that the computer would perform this verification step about 30-50 times per second. On a properly functioning computer this stress test should never fail, but surprisingly we discovered that on about 1% of the computers being used to play Guild Wars it did fail! One percent might not sound like a big deal, but when one million gamers play the game on any given day that means 10,000 would have at least one crash bug. Our programming team could spend weeks researching the bugs for just one day at that rate!'"
Link to Original Source
This discussion was created for logged-in users only, but now has been archived. No new comments can be posted.

Whose bug is this anyway?

Comments Filter:

"If truth is beauty, how come no one has their hair done in the library?" -- Lily Tomlin

Working...