GNU bug report logs - #48401
25.3; emacs27 crashes

Previous Next

Full log

Message #11 received at 48401 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Aloe <aloe <at> aloe-associacio.org>
Cc: 48401 <at> debbugs.gnu.org
Subject: Re: bug#48401: 25.3; emacs27 crashes
Date: Thu, 13 May 2021 20:28:32 +0300

> From: Aloe <aloe <at> aloe-associacio.org>
> Cc: 48401 <at> 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.

Previous Next

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