4 Feb
2019
4 Feb
'19
7:09 p.m.
On 02/04/2019 11:34 AM, Fritz Mueller via cctalk wrote:
OK, here's a really complicated thing to try. If you know
the physical memory address of ls when it has the problem,
write a machine language program that loads a copy of ls
into that location and then tries to read it back. You
might be able to do this in Unix, having it start with the
exact code of ls, but then has the tester above that and the
entry point is for the test program.
This would detect a pattern sensitivity in the memory. If
ls, when actually running reads an instruction wrong, it
could then try to read a bad address, and cause the MMU trap.
Jon
2. Make a copy of ls, and see if the copy also
fails
(different location on disk would mess with timing just a bit).
Also done; the
copy appears to behave identically to the original.