Dear Paul Gortmaker,
In message <1254521913-25655-1-git-send-email-paul.gortma...@windriver.com> you
wrote:
> The basic memtest function tries to watch for ^C after each
> pattern pass as an escape mechanism, but if things are horribly
> wrong, we'll be stuck in an inner loop flooding the console
On Friday 02 October 2009 18:18:33 Paul Gortmaker wrote:
> The basic memtest function tries to watch for ^C after each
> pattern pass as an escape mechanism, but if things are horribly
> wrong, we'll be stuck in an inner loop flooding the console with
> error messages and never check for ^C. To ma
The basic memtest function tries to watch for ^C after each
pattern pass as an escape mechanism, but if things are horribly
wrong, we'll be stuck in an inner loop flooding the console with
error messages and never check for ^C. To make matters worse,
if the user waits for all the error messages to
Mike Frysinger wrote:
> On Thursday 01 October 2009 19:52:27 Paul Gortmaker wrote:
>> if (iteration_limit && iterations > iteration_limit) {
>> -printf("Tested %d iteration(s) without errors.\n",
>> -iterations-1);
>> +
On Thursday 01 October 2009 19:52:27 Paul Gortmaker wrote:
> if (iteration_limit && iterations > iteration_limit) {
> - printf("Tested %d iteration(s) without errors.\n",
> - iterations-1);
> + printf("Tested %d itera
The basic memtest function tries to watch for ^C after each
pattern pass as an escape mechanism, but if things are horribly
wrong, we'll be stuck in an inner loop flooding the console with
error messages and never check for ^C. To make matters worse,
if the user waits for all the error messages to
6 matches
Mail list logo
