Very Remote Lisp Debugging Story
susam.net
susam.net
Lisping at JPL (2020) - https://news.ycombinator.com/item?id=28113434 - Aug 2021 (9 comments)
Lisping at JPL (2002) - https://news.ycombinator.com/item?id=22087419 - Jan 2020 (307 comments)
Lisping at JPL (2002) - https://news.ycombinator.com/item?id=17051503 - May 2018 (1 comment)
Lisping at JPL (2002) - https://news.ycombinator.com/item?id=13626074 - Feb 2017 (37 comments)
Lisping at JPL (2002) - https://news.ycombinator.com/item?id=7989328 - July 2014 (19 comments)
Lisping at the Jet Propulsion Lab - https://news.ycombinator.com/item?id=3773087 - March 2012 (1 comment)
The rise and fall of Lisp at the Jet Propulsion Lab (2002) - https://news.ycombinator.com/item?id=2212211 - Feb 2011 (36 comments)
The Rise and Fall of Lisp at the Jet Propulsion Lab. - https://news.ycombinator.com/item?id=304736 - Sept 2008 (72 comments)
But Ron wrote a simulator in lisp, and could verify the necessary procedure in his lisp simu. The C code was patched and the spacecraft survived the reboot. But after re-reading the paper I could have mixed it up, and lisp was indeed in space, and was only killed later.
I often remember his story, and often implement similar simus for my firmwares. And very often such a simu is the best tool to find bugs or to verify patches.
But it would be hard to identify any long-lived space probe whose software was not updated after launch. There are famous stories about Mars rovers.
Remote Agent was first for a) being able to be interactively debugged at remote b) actually exercising that, also c) IIRC it was already designed as basis to provide self-healing kind of ability to the system (or I might be confusing it with another lisp system from Ron Garret while he was at JPL)