3 ms·
You're right. The bug described in the article is just of the "may fail under load / with multiple users / in real-life scenarios" variety. In the zoology of b
by rolux 14y ago
You're right. The bug described in the article is just of the "may fail under load / with multiple users / in real-life scenarios" variety.
In the zoology of bugs, that makes it a common Mandelbug (1), but not a rare Heisenbug (2). For an even more exotic species, see Schroedinbug (3).
(1) http://www.catb.org/jargon/html/M/mandelbug.html http://www.catb.org/jargon/html/M/mandelbug.html
(2) http://www.catb.org/jargon/html/H/heisenbug.html http://www.catb.org/jargon/html/H/heisenbug.html
(3) http://www.catb.org/jargon/html/S/schroedinbug.html http://www.catb.org/jargon/html/S/schroedinbug.html
- Jare 14y agoI think the proper term for the bug is "race condition", since it is triggered by timing I first encountered this type of bug back in Z80 days. The fastest possible way to copy memory was using an unrolled sequence of POP/PUSH on the stack; however, if you forgot to disable interrupts while doing this, the data could be corrupted.