From: Robert Pluim <rpluim@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Aloe <aloe@aloe-associacio.org>, 48401@debbugs.gnu.org
Subject: bug#48401: 25.3; emacs27 crashes
Date: Wed, 19 May 2021 10:32:02 +0200 [thread overview]
Message-ID: <87v97f5dkt.fsf@gmail.com> (raw)
In-Reply-To: <834kf0rsok.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 18 May 2021 18:02:35 +0300")
>>>>> On Tue, 18 May 2021 18:02:35 +0300, Eli Zaretskii <eliz@gnu.org> said:
>> From: Aloe <aloe@aloe-associacio.org>
>> Cc: 48401@debbugs.gnu.org
>> Date: Tue, 18 May 2021 16:50:21 +0200
>>
>> Eli Zaretskii writes:
>>
>> >> From: Aloe <aloe@aloe-associacio.org>
>> >> Cc: 48401@debbugs.gnu.org
>> >> Date: Mon, 17 May 2021 21:05:53 +0200
>> >>
>> >> Thread 1 (Thread 0x7ffff7fb3a00 (LWP 24611)):
>> >> #0 __GI___pthread_mutex_lock (mutex=0x20) at ../nptl/pthread_mutex_lock.c:66
>> >> #1 0x00007ffff3d663ec in ?? () from /usr/lib/x86_64-linux-gnu/libgnutls.so.28
>> >> #2 0x00007ffff3df6c67 in ?? () from /usr/lib/x86_64-linux-gnu/libgnutls.so.28
>> >> #3 0x000000000056c795 in extract_data_from_object (spec=<optimized out>,
>> >> spec@entry=0x280ac63, start_byte=start_byte@entry=0x7fffffffa598,
>> >> end_byte=end_byte@entry=0x7fffffffa5a0) at fns.c:5290
>> >> #4 0x00000000005a06d1 in gnutls_symmetric (encrypting=<optimized out>,
>> >> ---Type <return> to continue, or q <return> to quit---
>> >> cipher=<optimized out>, key=0x280ac13, iv=0x280ac63, input=0x280ac03,
>> >> aead_auth=<optimized out>) at gnutls.c:2380
>> >> #5 0x000000000055e71b in Ffuncall (nargs=5, args=args@entry=0x7fffffffa698)
>> >> at eval.c:2795
>> >
>> > Looks like a problem in GnuTLS. Which version of GnuTLS do you have
>> > installed? Can you upgrade to a newer version?
>>
>> The output of gnutls-cli -v is:
>>
>> gnutls-cli (GnuTLS) 2.12.23
>> Packaged by Debian (2.12.23-12ubuntu2.8)
Eli> That's very strange, because line 5290 of fns.c should not have been
Eli> compiled unless you have GnuTLS 3.x.
Eli> In any case, 2.12.23 is very old.
Thatʼs gnutls-cli, not the gnutls development headers. I guess itʼs
possible to have new headers and an old gnutls-cli in
parallel. Something like
apt info libgnutls28-dev
would tell us which headers are installed. On my Debian system that
gives me:
Package: libgnutls28-dev
Version: 3.7.1-3
Robert
--
next prev parent reply other threads:[~2021-05-19 8:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-13 15:10 bug#48401: 25.3; emacs27 crashes Aloe
2021-05-13 16:47 ` Eli Zaretskii
2021-05-13 17:14 ` Aloe
2021-05-13 17:28 ` Eli Zaretskii
2021-05-13 17:54 ` Aloe
2021-05-13 19:12 ` Eli Zaretskii
2021-05-17 19:05 ` Aloe
2021-05-17 19:14 ` Eli Zaretskii
2021-05-18 9:15 ` Robert Pluim
2021-05-18 14:50 ` Aloe
2021-05-18 15:02 ` Eli Zaretskii
2021-05-18 18:03 ` Aloe
2021-05-19 8:32 ` Robert Pluim [this message]
2021-05-19 13:07 ` Aloe
2021-05-25 15:55 ` Aloe
2021-05-26 8:55 ` Robert Pluim
2021-05-26 15:25 ` Aloe
2021-06-24 16:23 ` Lars Ingebrigtsen
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87v97f5dkt.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=48401@debbugs.gnu.org \
--cc=aloe@aloe-associacio.org \
--cc=eliz@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).