code unit-tests with mocked clocks catch a lot of funky things like this. But you have to either know to test a piece of code, or be disciplined about testing _everything_ like that. And it doesn't retrofit into existing codebases well at all. On Sat, May 2, 2015 at 9:42 AM, Dave Taht wrote: > Somehow I really would like to be able to run a firmware's clock > forward WAY faster and transparently to catch bugs like this. > > > ---------- Forwarded message ---------- > From: David Farber > Date: Sat, May 2, 2015 at 7:41 AM > Subject: [IP] To keep a Boeing Dreamliner flying, reboot once every > 248 days A software bug again > To: ip > > > > > > http://www.engadget.com/2015/05/01/boeing-787-dreamliner-software-bug/#continued > < > http://www.engadget.com/2015/05/01/boeing-787-dreamliner-software-bug/#continued > > > > > ------------------------------------------- > Archives: https://www.listbox.com/member/archive/247/=now > RSS Feed: https://www.listbox.com/member/archive/rss/247/26973280-5ba6a701 > Modify Your Subscription: > > https://www.listbox.com/member/?member_id=26973280&id_secret=26973280-3b04af21 > Unsubscribe Now: > > https://www.listbox.com/unsubscribe/?member_id=26973280&id_secret=26973280-063e9b28&post_id=20150502104110:446F186A-F0D9-11E4-B42B-AC84EB0E84BC > Powered by Listbox: http://www.listbox.com > > > -- > Dave Täht > Open Networking needs **Open Source Hardware** > > https://plus.google.com/u/0/+EricRaymond/posts/JqxCe2pFr67 > _______________________________________________ > Cerowrt-devel mailing list > Cerowrt-devel@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/cerowrt-devel >