The DOS Bug That Almost Killed The Spirit Mars Rover - Slashdot

Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

Check out the new SourceForge HTML5 internet speed test! No Flash necessary and runs on all devices. ×

Submission + - The DOS Bug That Almost Killed The Spirit Mars Rover (itworld.com) 3

Submitted by

jfruh

on Tuesday January 29, 2013 @12:21PM

jfruh writes: "On January 21, 2004, the Spirit Mars rover, which had been cheerfully collecting data and sending it back to Earth for the two weeks since it had landed, suddenly ground to a halt. Mission controllers at the Jet Propulsion Laboratory were getting pings indicating that the rover was alive, but that was it. Over the next eleven days, the JPL team coaxed the rover back to life, eventually discovering that the heart of the problem lay in a DOS memory management bug interacting with insufficiently tested third-party code."

This discussion was created for logged-in users only, but now has been archived. No new comments can be posted.

The DOS Bug That Almost Killed The Spirit Mars Rover

Load All Comments

Search 3 Comments Log In/Create an Account

Comments Filter:

Not a "DOS bug" (Score:1)

by Megane ( 129182 ) writes:

TFA says "DOS-related" bug. The bug was in a FAT filesystem library. The only thing MS-DOS had to do with it was being the origin of the FAT filesystem.
Also, why now? (Score:1)

by Megane ( 129182 ) writes:

I can find no new information in the article. It seems it was only written because this was an anniversary of the landing. A ninth anniversary no less. Stale!
- Information here ... (Score:2)
  
  by Taco Cowboy ( 5327 ) writes:
  
  TFA was written by someone who has no idea about computer
  The info on the bug is as follow:
  http://en.wikipedia.org/wiki/Spirit_rover#Sol_17_.28January_21.2C_2004.29_flash_memory_management_anomaly [wikipedia.org]

There may be more comments in this discussion. Without JavaScript enabled, you might want to turn on Classic Discussion System in your preferences instead.

It is much easier to suggest solutions when you know nothing about the problem.