Bug#824901: [pkg-gnupg-maint] Bug#824901: gnupg: gpg segfaults

2016-05-22 Thread Christoph Egger
Werner Koch writes: > On Sat, 21 May 2016 19:48, christ...@christoph-egger.org said: >> % gdb --args gpg --debug-all --list-sigs 0x3B78A32D98BAD5B0 > >> Program received signal SIGSEGV, Segmentation fault. >> _gcry_log_printmpi (text=text@entry=0x55606606 "pkey[0]", >> mpi=0x3e67726f2e) at ..

Bug#824901: [pkg-gnupg-maint] Bug#824901: gnupg: gpg segfaults

2016-05-22 Thread Werner Koch
On Sat, 21 May 2016 19:48, christ...@christoph-egger.org said: > % gdb --args gpg --debug-all --list-sigs 0x3B78A32D98BAD5B0 > Program received signal SIGSEGV, Segmentation fault. > _gcry_log_printmpi (text=text@entry=0x55606606 "pkey[0]", > mpi=0x3e67726f2e) at ../../src/misc.c:337 Accordin

Bug#824901: [pkg-gnupg-maint] Bug#824901: gnupg: gpg segfaults

2016-05-21 Thread Christoph Egger
Hi! Werner Koch writes: > however, we don't have debug symbols for Libgcrypt. I'd suggest to try > this patch for debugging: Actually unstable-debug has. Anyway (can give full log if that's needed as well > diff --git a/g10/seskey.c b/g10/seskey.c > index c41a145..d0e6b6f 100644 > --- a/g10/se

Bug#824901: [pkg-gnupg-maint] Bug#824901: gnupg: gpg segfaults

2016-05-21 Thread Werner Koch
On Sat, 21 May 2016 04:56, christ...@christoph-egger.org said: > GPG seems to reproducibly segfault on the command below (at least on > my box). I had a segfault on gpg --import earlier as well but couln't I can't replicate that here. The culprit seems to be either gcry_md_get_algo_dlen (has