GNU bug report logs - #24811
Waiting to answer s at untrusted cert dialog causes crash

Previous Next

Full log

View this message in rfc822 format

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: Mark Oteiza <mvoteiza <at> udel.edu>
Cc: 24811 <at> debbugs.gnu.org
Subject: bug#24811: 26.0.50; backtrace
Date: Fri, 28 Oct 2016 09:47:55 +0200

Mark Oteiza <mvoteiza <at> udel.edu> writes:

> 1. M-x eww RET https://marmalade-repo.org RET
>
> The certificate is signed by Comodo, which is an untrusted CA on my
> system.  At this point, NSM pops up asking how I want to proceed.
>
> 2. Wait for a while. A minute here is sufficient.
> 3. Hit s to allow the cert for the session only.
>
> Emacs has now crashed:
>
> #0  0x00007f8dc27ba04f in raise () at /usr/lib/libc.so.6
> #1  0x00007f8dc27bb47a in abort () at /usr/lib/libc.so.6
> #2  0x00007f8dc27f7c50 in __libc_message () at /usr/lib/libc.so.6
> #3  0x00007f8dc287ff17 in __fortify_fail () at /usr/lib/libc.so.6
> #4  0x00007f8dc287e050 in __readonly_area () at /usr/lib/libc.so.6
> #5  0x00007f8dc287fe8a in  () at /usr/lib/libc.so.6
> #6  0x0000000000595a43 in fd_ISSET (set=0xbfa8e0 <connect_wait_mask>, fd=-1)
>     at sysselect.h:72
> #7  0x0000000000595a43 in finish_after_tls_connection (proc=proc <at> entry=65073861)
>     at process.c:3102

Oh, interesting.  I would guess the wait makes the remote party close
the connection, but there's no check in finish_after_tls_connection that
the socket still exists.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.