in reply to Re: SUPER delegation fails because class name getting munged (somehow?)
in thread SUPER delegation fails because class name getting munged (somehow?)

O is decimal 79 is binary 01001111, P is decimal 80 is binary 01010000. So this is not bit flipping, there is something really substracting 1
  • Comment on Re^2: SUPER delegation fails because class name getting munged (somehow?)

Replies are listed 'Best First'.
Re^3: SUPER delegation fails because class name getting munged (somehow?)
by Eliya (Vicar) on Feb 23, 2011 at 17:23 UTC

    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.

      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.

        Not necessarily. The corruption could be in the address used by some unrelated decrement.

        It does seem rather predictable for hardware memory corruption, though.