Re^3: SUPER delegation fails because class name getting munged (somehow?)

Ok, my fault. The "argument" still holds, though, as hardware memory corruption mustn't necessarily result in only single bits flipping — it just happened to begin that way in the limited number of cases I've observed so far. I.e., the memtest statistics (after running for a couple of days) showed a clear pattern of certain "bit lines" flipping far more frequently than others.

Comment on Re^3: SUPER delegation fails because class name getting munged (somehow?)

Replies are listed 'Best First'.
Re^4: SUPER delegation fails because class name getting munged (somehow?) by jethro (Monsignor) on Feb 23, 2011 at 19:04 UTC
Flipping of more than one bit is possible and probably quite common, but to have bits flip so that always a substraction of 1 comes out is just very unlikely. I did check the other two examples and while one was similar to the case I posted about, the other one was just a flip of the lowest bit.	[reply]
Re^5: SUPER delegation fails because class name getting munged (somehow?) by ikegami (Patriarch) on Feb 24, 2011 at 18:44 UTC
Not necessarily. The corruption could be in the address used by some unrelated decrement. It does seem rather predictable for hardware memory corruption, though.	[reply]