From: Aloe <aloe@aloe-associacio.org>
To: "Eli Zaretskii" <eliz@gnu.org>
Cc: 48401@debbugs.gnu.org
Subject: bug#48401: 25.3; emacs27 crashes
Date: Thu, 13 May 2021 19:54:36 +0200 [thread overview]
Message-ID: <87mtsymsdf.fsf@aloe-associacio.org> (raw)
In-Reply-To: <8335uq1r27.fsf@gnu.org>
Eli Zaretskii writes:
>> From: Aloe <aloe@aloe-associacio.org>
>> Cc: 48401@debbugs.gnu.org
>> Date: Thu, 13 May 2021 19:14:30 +0200
>>
>> Hi, thanks for your answer, that's my backtrace:
>>
>> emacs_backtrace a /usr/share/emacs27/src/sysdep.c:2443
>> terminate_due_to_signal a /usr/share/emacs27/src/emacs.c:404
>> handle_fatal_signal a /usr/share/emacs27/src/sysdep.c:1795
>> deliver_thread_signal.constprop.9 a /usr/share/emacs27/src/sysdep.c:1769
>> stack_overflow a /usr/share/emacs27/src/sysdep.c:1829
>> (inserit per) handle_sigsegv a /usr/share/emacs27/src/sysdep.c:1888
>> ?? ??:0
>> ?? ??:0
>> ?? ??:0
>> ?? ??:0
>> extract_data_from_object a /usr/share/emacs27/src/fns.c:5293
>> gnutls_symmetric a /usr/share/emacs27/src/gnutls.c:2382
>> Ffuncall a /usr/share/emacs27/src/eval.c:2795
>> exec_byte_code a /usr/share/emacs27/src/bytecode.c:633
>> Ffuncall a /usr/share/emacs27/src/eval.c:2818
>> exec_byte_code a /usr/share/emacs27/src/bytecode.c:633
>> Ffuncall a /usr/share/emacs27/src/eval.c:2818
>> exec_byte_code a /usr/share/emacs27/src/bytecode.c:633
>> Ffuncall a /usr/share/emacs27/src/eval.c:2818
>> SPECPDL_INDEX a /usr/share/emacs27/src/lisp.h:3279
>> (inserit per) Fapply a /usr/share/emacs27/src/eval.c:2373
>> Ffuncall a /usr/share/emacs27/src/eval.c:2795
>> exec_byte_code a /usr/share/emacs27/src/bytecode.c:633
>> Ffuncall a /usr/share/emacs27/src/eval.c:2818
>> exec_byte_code a /usr/share/emacs27/src/bytecode.c:633
>> Ffuncall a /usr/share/emacs27/src/eval.c:2818
>> exec_byte_code a /usr/share/emacs27/src/bytecode.c:633
>> Ffuncall a /usr/share/emacs27/src/eval.c:2818
>> exec_byte_code a /usr/share/emacs27/src/bytecode.c:633
>> Ffuncall a /usr/share/emacs27/src/eval.c:2818
>> exec_byte_code a /usr/share/emacs27/src/bytecode.c:633
>> Ffuncall a /usr/share/emacs27/src/eval.c:2818
>> exec_byte_code a /usr/share/emacs27/src/bytecode.c:633
>> Ffuncall a /usr/share/emacs27/src/eval.c:2818
>> exec_byte_code a /usr/share/emacs27/src/bytecode.c:633
>> Ffuncall a /usr/share/emacs27/src/eval.c:2818
>> exec_byte_code a /usr/share/emacs27/src/bytecode.c:633
>> Ffuncall a /usr/share/emacs27/src/eval.c:2818
>> exec_byte_code a /usr/share/emacs27/src/bytecode.c:633
>> Ffuncall a /usr/share/emacs27/src/eval.c:2818
>> exec_byte_code a /usr/share/emacs27/src/bytecode.c:633
>> Ffuncall a /usr/share/emacs27/src/eval.c:2818
>> exec_byte_code a /usr/share/emacs27/src/bytecode.c:633
>>
>>
>> I hope it's what your are asking for.
>
> It is, thanks.
>
> This looks like infinite recursion, so I think we will need a more
> detailed backtrace which you can obtain by running Emacs under GDB.
> Would it be possible for you to do that? Let me know if you need
> instructions.
Yes, please give me instructions. I can open GDB but I don't know how to
backtrace.
Thanks
--
Associació Lliure d'Orientació Educativa (A.L.O.E.)
c/ Miquel Romeu, 93. 1r.
08907- L'Hospitalet de Ll.
93.261.13.58 - 674.831.973
http://www.aloe-associacio.org
next prev parent reply other threads:[~2021-05-13 17:54 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 [this message]
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
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=87mtsymsdf.fsf@aloe-associacio.org \
--to=aloe@aloe-associacio.org \
--cc=48401@debbugs.gnu.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).