Charles-François Natali added the comment: 2013/8/30 Martin Mokrejs <rep...@bugs.python.org>: > Per comment from Charles-François, so you mean that this single-bit change > won't be caught by valgrind, right? Why does not memtest86+ detect that? > Could python when compiled with the --with-pydebug print also physical, > hardware address of the wrong value? That would be really helpful here! > Thanks.
I mean that in the vast majority of cases, a single bit flip is due to a hardware error. That can be due to faulty RAM, electric noise, cosmic rays... Software-induced memory corruptions generally corrupt at least a byte. Do you reproduce the crash systematically, or is it random? ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue18843> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
