Date: Thu, 23 Oct 2014 21:37:40 -0800 From: Royce Williams <royce@...ho.org> To: john-dev <john-dev@...ts.openwall.com> Subject: Re: "Failed copy data to gpu" when using fork with descrypt-opencl On Sun, Oct 19, 2014 at 11:06 AM, magnum <john.magnum@...hmail.com> wrote: > On 2014-10-19 18:07, Royce Williams wrote: >> What is the recommended way to tell 'git bisect' to ignore Makefiles >> generated by ./configure? > > Just delete the file after building and/or check out the stub again. I'm not > very happy with the current Makefile mess, maybe we should drop that stub. This helped, but there's too many other factors across the commit (compilation failures, etc.) to really zoom in properly -- at my levels of git skill and cycles right now, anyway. If I ignore 'Self test failed (get_hash(3))' errors and bisect accordingly, I get too many hits to be useful (as far as I can tell): There are only 'skip'ped commits left to test. The first bad commit could be any of: 6a1b264a246ccc41b2dcacfd2d67104bd25c682b 903080a1d1d09890e65a571f973ae59486bc42b1 1fd4e25263f63eb0ac64774b9a91b76b331b2aa0 7c4207f3f48d6a5e63c18cc0c1d518d1dc714184 13deb3cd9caf433bdfea66b9d259b2f06412cd77 9f982851fedb751fd32d4d28f0b64011a5f67f30 fc285c765a0b4d20a36c4f143e108906eb38b37f fe93814d901215b8c3c141f700caacaa2a4db7dc e1b390e73b305fb38ad4fd01be3a9174d8e30010 We cannot bisect more! bisect run cannot continue any more I also got the following error on recent makes, but do not know if it's relevant or not: DES_std.c: In function ‘DES_std_set_key’: DES_std.c:637:17: warning: array subscript is above array bounds [-Warray-bounds] while (DES_key[i++]) k += 2; So I'm stuck on how to move past my 'Failed Copy data to gpu' error. The consequence is that I can only use one CPU core to send candidate passwords to descrypt-opencl. Is anyone else seeing this? Royce
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.