Re:Bug of the Year (2011)
by woliveirajr on Thursday February 01, 2018 @09:32AM
(#16282064)
Ah, just two processors without clock syncronization. Fast-forward 6 years and we have ways to explore memory that was cached for instructions that won't be executed, and leak the hell of the processors' hearts.
Re:Bug of the Year (2011)
by mharsch on Thursday February 01, 2018 @12:08PM
(#16283526)
This article pairs nicely with bcantrill's recently released talk "The Hurricane's Butterfly: Debugging Pathologically Performing Systems" https://youtu.be/7AO4wz6gI3Q
Re:Bug of the Year (2011)
by tomxor on Thursday February 01, 2018 @01:34PM
(#16284412)
It's always fun when you get to the bottom of one of these and find out some seemingly absurd mistake or design flaw, each layer peeled away reveals a new level of excitement. Even when it's not in hardware it opens up your eyes about the potential fallibility of all the layers beneath whatever you are doing.
http://web.mit.edu/jemorris/humor/500-miles
http://beza1e1.tuxen.de/lore/print_on_tuesday.html