From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 87071] LLVM triggered Diagnostic Handler: unsupported call to function S2KItSaltedSHA1Generator in gpg
Date: Sun, 07 Dec 2014 13:04:44 +0000 [thread overview]
Message-ID: <bug-87071-502-PLJW8Peu2H@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-87071-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 589 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=87071
--- Comment #1 from Dennis Schridde <devurandom@gmx.net> ---
P.S: John's complete output is:
# /usr/sbin/john --format=gpg-opencl […]
Device 0: AMD REDWOOD
Build log: �
Local worksize (LWS) 64, Global worksize (GWS) 8192
Loaded 1 password hash (gpg-opencl, OpenPGP / GnuPG Secret Key [SHA1 OpenCL])
Will run 2 OpenMP threads
LLVM triggered Diagnostic Handler: unsupported call to function
S2KItSaltedSHA1Generator in gpg
Segmentation fault
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1468 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2014-12-07 13:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-07 13:03 [Bug 87071] LLVM triggered Diagnostic Handler: unsupported call to function S2KItSaltedSHA1Generator in gpg bugzilla-daemon
2014-12-07 13:04 ` bugzilla-daemon [this message]
2016-08-25 2:16 ` bugzilla-daemon
2017-03-15 14:16 ` bugzilla-daemon
2018-05-30 7:09 ` [Bug 87071] [clover/redwood] John the Ripper: " bugzilla-daemon
2019-09-18 19:18 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-87071-502-PLJW8Peu2H@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.