From: Eli Zaretskii <eliz@gnu.org>
To: Aloe <aloe@aloe-associacio.org>
Cc: 48401@debbugs.gnu.org
Subject: bug#48401: 25.3; emacs27 crashes
Date: Thu, 13 May 2021 22:12:29 +0300 [thread overview]
Message-ID: <83zgwyzbvm.fsf@gnu.org> (raw)
In-Reply-To: <87mtsymsdf.fsf@aloe-associacio.org> (message from Aloe on Thu, 13 May 2021 19:54:36 +0200)
> From: Aloe <aloe@aloe-associacio.org>
> Cc: 48401@debbugs.gnu.org
> Date: Thu, 13 May 2021 19:54:36 +0200
>
> > 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.
Go to the directory where you have the Emacs sources (assuming you
have them on your system), then type at the shell prompt
$ gdb emacs
When you get to the "(gdb)" prompt, type "run". Emacs should start as
usual, and then do whatever you need to reproduce the problem. When
Emacs crashes, GDB will kick in and show its "(gdb)" prompt where you
started it. Then type at GDB's prompt:
thread apply all bt
This will produce backtraces of all the threads in the Emacs process.
Post the output here.
next prev parent reply other threads:[~2021-05-13 19:12 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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83zgwyzbvm.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=48401@debbugs.gnu.org \
--cc=aloe@aloe-associacio.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.