On 04/07/2018 09:17, Michał Pleban wrote: > That would be too early. We don't want to find what heppens when the CPU > _starts_ testing the RAM. We want to find out what caused the CPU to > _stop_ testing the RAM - that's when the error occurs. And we don't know > when it really occurs. Can you have it store the signals in a ring buffer until it fetches the instruction in the failure path of the code?Received on 2018-07-04 21:02:21
Archive generated by hypermail 2.2.0.