I think we should keep this bug open to provide a better error message.
Martin said: "As Robert said, this is almost always a hardware error."
AFAIK, we still haven't encountered a case where it *wasn't* an hardware error, so we may as well point that in the error message, if it turns out that we *can* produce such bogus data, then that will be another bug to fix.
I think we should keep this bug open to provide a better error message.
Martin said: "As Robert said, this is almost always a hardware error."
AFAIK, we still haven't encountered a case where it *wasn't* an hardware error, so we may as well point that in the error message, if it turns out that we *can* produce such bogus data, then that will be another bug to fix.