Message 196518 - Python tracker

Just two things:
- running under valgrind with the suppression file would help pinpoint this
- usually, stack/heap overflows or invalid pointer dereference affect a contiguous chunk of memory: here, there's a *single bit* flipped, not even a byte
0xfb == 0b11111011
0xfa == 0b11111010

This looks like an hardware issue to me.