[Pkg-gnupg-maint] Bug#776611: Bug#776611: [dirmngr] segfaults
Daniel Kahn Gillmor
dkg at fifthhorseman.net
Thu Jan 29 23:20:12 UTC 2015
Control: tags 776611 + unreproducible moreinfo
On Thu 2015-01-29 17:22:00 -0500, Florian Reitmeir wrote:
> Package: dirmngr
> Version: 1.1.1-4
> Severity: serious
>
> i really do not know how to debug it, but .. it always segfaults.
>
> [ 14.070905] dirmngr[2239]: segfault at 2 ip 00007f5cda9b9ff6 sp
> 00007ffffd09e130 error 4 in libc-2.19.so[7f5cda981000+19f000]
[...]
> [ 444.735631] dirmngr[5172]: segfault at 2 ip 00007fadea76fff6 sp
> 00007fff21acd780 error 4 in libc-2.19.so[7fadea737000+19f000]
hm, i'm assuming that because this happens very early, this is the
system dirmngr process that is segfaulting.
I've got this same version running on an amd64 system with libassuan
2.1.2-2 as well, but i'm not seeing these segfaults.
Can you send this bug report (or me privately, if you think it's
sensitive) the contents of /var/log/dirmngr/dirmngr.log ?
If that doesn't provide a useful hint, you might try halting the system
service and launching it by hand under strace (as the superuser):
systemctl stop dirmngr
strace -f -o /root/dirmngr.strace su - dirmngr -c '/usr/bin/dirmngr --daemon --sh'
if it crashes at that point, you can send on /root/dirmngr.strace.
If all of the above is fruitless, and you want to keep trying, can i get
you to rebuild the package with debug symbols (DEB_BUILD_OPTIONS=nostrip
should work) and install libc6-dbg and capture a coredump to get a
backtrace?
Thanks for the report,
--dkg
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 948 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-gnupg-maint/attachments/20150129/fbd2b6c3/attachment.sig>
More information about the Pkg-gnupg-maint
mailing list