Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <50F171CC.5020505@gmail.com>
Date: Sat, 12 Jan 2013 12:23:08 -0200
From: Claudio André <claudioandre.br@...il.com>
To: john-dev@...ts.openwall.com
Subject: Re: SIGALRM and new 'done' method

Em 12-01-2013 12:20, magnum escreveu:
> On 12 Jan, 2013, at 15:15 , Claudio André <claudioandre.br@...il.com> wrote:
>> Em 12-01-2013 11:56, magnum escreveu:
>>> On 12 Jan, 2013, at 14:55 , magnum <john.magnum@...hmail.com> wrote:
>>>> I could reproduce the initial SIGALRM problem we had before 3040fc9 by forcing OS_TIMER=0 in arch.h but I can't reproduce this one. And I really can't see how 4a7c6df could fail to resolve the issue.
>>>>
>>>> Does this only ever happen when testing several (ie. all) formats? If so, that is likely a clue.
>>> Oh and BTW, are you using --test=0 or just --test, or something else?
>>>
>>> magnum
>>>
>> make *-opencl
>> ../run/john -t
> Try -t=0, it's a LOT faster but you don't get proper speed results (at least not for CPU formats).
>
>> Only see it when testing several (ie. all) formats.
>>
>> Hey, it is OSS.
>> - git clone git@...hub.com:claudioandre/JohnTheRipper.git
>>
>> master branch.
> I already did :)  But like I said, I can't reproduce it on OSX. It's signal() function remains installed after a signal has been delivered.
>
> magnum

The last time i tried it on bull, it failed.

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.