New submission from Kåre Krig karek...@gmail.com:
When I concatenate two strings, with the one on the right hand side being
large, the resulting string is almost correct but has a few chars substituted.
The following code (with (...) added on the print statement for 3.1) prints
False on both
Antoine Pitrou pit...@free.fr added the comment:
Have you tried with other large files? Or on another system?
--
nosy: +pitrou
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12784
___
Changes by STINNER Victor victor.stin...@haypocalc.com:
--
nosy: +haypo
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12784
___
___
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +ezio.melotti
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12784
___
___
STINNER Victor victor.stin...@haypocalc.com added the comment:
Try hash(buff_A) == hash(buff_B).
Are you able to identify which bytes/characters are differents?
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12784
Kåre Krig karek...@gmail.com added the comment:
I tried it again with another file. This time I used the dictionary from
www.math.sjsu.edu/~foster/dictionary.txt (~3Mb)
hash(buff_A) == hash(buff_B) returns False just like the direct comparison. I
ran the program on dictionary.txt and
Antoine Pitrou pit...@free.fr added the comment:
Note how the ascii codes for the faulty characters only differ by one
bit, and only the 5th least significant bit.
This looks very much like a hardware issue.
Python usually does nothing special with the 5th bit of characters. Also, the
IO
STINNER Victor victor.stin...@haypocalc.com added the comment:
You should retry memtest86+: http://www.memtest.org/#downiso
I had also memory errors recently. After 10 minutes, memtest86+ listed me 4
errors. After 30 minutes, there were 30 errors.
--
Kåre Krig karek...@gmail.com added the comment:
I managed to get access to another two systems to test this on. One running
ubuntu python 2.7.1 and the other suse python 2.6. I could not reproduce
the bug on either of those systems.
This all points to the issue not really being a bug in
STINNER Victor victor.stin...@haypocalc.com added the comment:
It's an hardware problem, not a Python problem, so I close this issue. Check
your RAM and the temperature of your mother board and of the CPU using your
tests (e.g. try lm-sensors on Linux).
--
resolution: - invalid
10 matches
Mail list logo
