[Bug 204399] security/keepassx2 bus error
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Mon Nov 9 13:49:07 UTC 2015
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204399
Bug ID: 204399
Summary: security/keepassx2 bus error
Product: Ports & Packages
Version: Latest
Hardware: amd64
OS: Any
Status: New
Severity: Affects Some People
Priority: ---
Component: Individual Port(s)
Assignee: freebsd-ports-bugs at FreeBSD.org
Reporter: lbolmerg at posteo.de
CC: eric at camachat.org
Flags: maintainer-feedback?(eric at camachat.org)
CC: eric at camachat.org
security/keepassx2-2.0.b2,1 receives signal SIGBUS immediately after
invocation.
system: 10.2-STABLE amd64, everything installed from packages
bug maybe related to https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196674
workaround: compile security/libgcrypt with Option -O0
...
Program received signal SIGBUS, Bus error.
[Switching to Thread 806807400 (LWP 100540/keepassx)]
0x0000000801dd6c74 in _gcry_salsa20_amd64_encrypt_blocks ()
from /usr/local/lib/libgcrypt.so.20
(gdb) bt
#0 0x0000000801dd6c74 in _gcry_salsa20_amd64_encrypt_blocks ()
from /usr/local/lib/libgcrypt.so.20
#1 0x0000000000000001 in ?? ()
#2 0x00000000002d0a00 in ?? ()
#3 0x000000080680758c in ?? ()
#4 0x0000000000000002 in ?? ()
#5 0x00007fffffffde80 in ?? ()
#6 0x0000000803625ae5 in pthread_getspecific () from /lib/libthr.so.3
#7 0x0000000801dd5c08 in _gcry_camellia_aesni_avx2_cfb_dec ()
from /usr/local/lib/libgcrypt.so.20
#8 0x0000000801dd563b in _gcry_camellia_aesni_avx2_cfb_dec ()
from /usr/local/lib/libgcrypt.so.20
#9 0x0000000801d706ae in gcry_is_secure () from /usr/local/lib/libgcrypt.so.20
#10 0x0000000801d6448f in gcry_cipher_setkey ()
from /usr/local/lib/libgcrypt.so.20
#11 0x000000000042ec17 in _start ()
#12 0x000000000042e85c in _start ()
#13 0x000000000042e333 in _start ()
#14 0x000000000042cda1 in _start ()
#15 0x0000000000423921 in _start ()
#16 0x000000000042378f in _start ()
#17 0x00000008006e6000 in ?? ()
#18 0x0000000000000000 in ?? ()
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-ports-bugs
mailing list