From: Eli Zaretskii <eliz@gnu.org>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: acm@muc.de, 48337@debbugs.gnu.org
Subject: bug#48337: Fwd: 28.0.50; Emacs crashing randomly (possibly minibuffer activity related)
Date: Tue, 11 May 2021 05:24:28 +0300 [thread overview]
Message-ID: <83fsyu57oj.fsf@gnu.org> (raw)
In-Reply-To: <CAHDbmO01fX5RqDKNm12q6kuhcMGh2TqZMeGD7oZs0VXmv8gOzA@mail.gmail.com> (message from Alex Bennée on Mon, 10 May 2021 20:30:58 +0100)
> From: Alex Bennée <alex.bennee@linaro.org>
> Date: Mon, 10 May 2021 20:30:58 +0100
> Cc: Alan Mackenzie <acm@muc.de>
>
> It seems my mail client left this in the sent folder but never actually sent it:
>
> I haven't been able to find a reproduction as the bug hits fairly
> randomly hence I'm running in my normal init.el heavy environment.
> That said there shouldn't be anything in lisp that could cause a
> segfault in the core C code.
>
> This only started happening this week after a recent update from
> master (I update every Monday). The only change I could see that might
> be related was f608b4b93 (Prevent the selected window being a dead
> mini-window when switching frames).
>
> Unfortunately no symbols. However both core dumps so far have seen the
> same null XCAR being called from nth_minibuffer:
>
> #0 0x00007f4384f585cb in raise (sig=sig@entry=11) at ../sysdeps/unix/sysv/linux/raise.c:50
> set = {__val = {18446744067266837247, 0 <repeats 15 times>}}
> pid = <optimized out>
> tid = <optimized out>
> #1 0x000055b6738bf530 in terminate_due_to_signal (sig=sig@entry=11,
> backtrace_limit=backtrace_limit@entry=40) at emacs.c:437
> #2 0x000055b6738bf97d in handle_fatal_signal (sig=sig@entry=11) at sysdep.c:1762
> #3 0x000055b6739b8ca8 in deliver_thread_signal (sig=sig@entry=11, handler=0x55b6738bf972
> <handle_fatal_signal>) at sysdep.c:1754
> #4 0x000055b6739b8d29 in deliver_fatal_thread_signal (sig=11) at sysdep.c:1867
> fatal = <optimized out>
> #5 0x000055b6739b8d29 in handle_sigsegv (sig=11, siginfo=<optimized out>, arg=<optimized out>) at
> sysdep.c:1867
> fatal = <optimized out>
> #6 0x00007f4384f58730 in <signal handler called> () at /lib/x86_64-linux-gnu/libpthread.so.0
> #7 0x000055b6739ce0ef in XCAR (c=0x0) at lisp.h:1420
> tail = 0x0
> frames = <optimized out>
> frame = <optimized out>
> f = <optimized out>
> innermost_MB = <optimized out>
> #8 0x000055b6739ce0ef in nth_minibuffer (depth=<optimized out>) at minibuf.c:972
> tail = 0x0
> frames = <optimized out>
> frame = <optimized out>
> f = <optimized out>
> innermost_MB = <optimized out>
Please show the Lisp value of Vminibuffer_list.
next prev parent reply other threads:[~2021-05-11 2:24 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87tunasd2u.fsf@linaro.org>
2021-05-10 19:30 ` bug#48337: Fwd: 28.0.50; Emacs crashing randomly (possibly minibuffer activity related) Alex Bennée
2021-05-10 19:34 ` bug#48337: Alex Bennée
2021-05-11 2:24 ` Eli Zaretskii [this message]
2021-05-11 6:51 ` bug#48337: Fwd: 28.0.50; Emacs crashing randomly (possibly minibuffer activity related) Alex Bennée
2021-05-11 8:23 ` Alex Bennée
2021-05-11 8:54 ` Alex Bennée
2021-05-11 12:21 ` Eli Zaretskii
2021-05-11 12:54 ` Alex Bennée
2021-05-11 13:42 ` Eli Zaretskii
2021-05-11 13:47 ` Eli Zaretskii
2021-05-11 19:45 ` Alan Mackenzie
2021-05-11 19:55 ` Eli Zaretskii
2021-05-12 18:54 ` Alan Mackenzie
2021-05-13 7:54 ` martin rudalics
2021-05-13 9:52 ` Alan Mackenzie
2021-05-13 11:54 ` Alan Mackenzie
2021-05-13 12:09 ` Alan Mackenzie
2021-05-14 15:20 ` Gregory Heytings
2021-05-14 16:05 ` Eli Zaretskii
2021-05-14 17:31 ` Gregory Heytings
2021-05-14 18:19 ` Eli Zaretskii
2021-05-15 9:45 ` Gregory Heytings
2021-05-11 20:14 ` Alan Mackenzie
2021-05-11 22:07 ` Alex Bennée
2021-05-14 16:31 ` Alan Mackenzie
2021-05-14 16:52 ` Alex Bennée
2021-05-14 18:40 ` Alan Mackenzie
2021-05-14 22:35 ` Alex Bennée
2021-05-15 12:00 ` Alan Mackenzie
2021-05-16 14:24 ` Alan Mackenzie
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=83fsyu57oj.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=48337@debbugs.gnu.org \
--cc=acm@muc.de \
--cc=alex.bennee@linaro.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).