[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <e32a2b65d10d7108ef152dd422980312@smtp.hushmail.com>
Date: Wed, 27 Jun 2012 21:01:51 +0200
From: magnum <john.magnum@...hmail.com>
To: john-dev@...ts.openwall.com
Subject: Re: "max run-time reached"
On 2012-06-27 18:30, Solar Designer wrote:
> On Tue, Jun 26, 2012 at 09:16:35AM +0200, magnum wrote:
>> On 2012-06-26 05:07, Solar Designer wrote:
>>> Benchmarking: FreeBSD MD5 [128/128 XOP intrinsics 8x]... ^CWait...
>>> Session stopped (max run-time reached)
>>
>> Yes that is ugly, introduced with --max-run-time. It happens if you
>> break before we "start the clock". I think I'd need another global to
>> work around it. I'll have a look.
>
> In another message you wrote that you fixed that, but I am still seeing
> the exact same problem (that message printed on interrupted benchmark).
I now committed the attached patch. I hope it's really impossible now.
magnum
View attachment "diff.txt" of type "text/plain" (662 bytes)
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
