From: Vincenzo Pupillo <v.pupillo@gmail.com>
To: Stefan Kangas <stefan@marxist.se>,
Gregory Heytings <gregory@heytings.org>
Cc: 47774@debbugs.gnu.org
Subject: bug#47774: 28.0.50; crash when using minibuffer
Date: Wed, 14 Apr 2021 21:37:11 +0200 [thread overview]
Message-ID: <2196410.ElGaqSPkdT@localhost.localdomain> (raw)
In-Reply-To: <7d9667a70fe2e2042930@heytings.org>
Sorry, I forgot to attach the stack trace (emacs crashed even during my first bug report :-(, the stack trace is the same).
No problem with emacs 27.2 . Now I'm trying to reproduce the bug with emacs -Q.
apr 14 11:45:41 localhost.localdomain systemd-coredump[174597]: Process 174371 (emacs) of user 1000 dumped core.
Stack trace of thread 174371:
#0 0x00007f283ae92065 raise (libpthread.so.0 + 0x14065)
#1 0x0000000000427f23 terminate_due_to_signal (emacs-28.0.50 + 0x27f23)
#2 0x000000000042857b handle_fatal_signal (emacs-28.0.50 + 0x2857b)
#3 0x0000000000640251 deliver_thread_signal.constprop.0 (emacs-28.0.50 + 0x240251)
#4 0x00007f283ae921e0 __restore_rt (libpthread.so.0 + 0x141e0)
#5 0x000000000054f25e read_minibuf_unwind (emacs-28.0.50 + 0x14f25e)
#6 0x00000000005a7194 unbind_to (emacs-28.0.50 + 0x1a7194)
#7 0x0000000000557c2b read_minibuf (emacs-28.0.50 + 0x157c2b)
#8 0x000000000055868b Fread_from_minibuffer (emacs-28.0.50 + 0x15868b)
#9 0x00000000005a6c22 funcall_subr (emacs-28.0.50 + 0x1a6c22)
#10 0x00000000005a7df1 Ffuncall (emacs-28.0.50 + 0x1a7df1)
#11 0x00000000005e74f1 exec_byte_code (emacs-28.0.50 + 0x1e74f1)
#12 0x00000000005a7d25 Ffuncall (emacs-28.0.50 + 0x1a7d25)
#13 0x00000000005e74f1 exec_byte_code (emacs-28.0.50 + 0x1e74f1)
#14 0x00000000005a7d25 Ffuncall (emacs-28.0.50 + 0x1a7d25)
#15 0x00000000005a7e45 Ffuncall_interactively (emacs-28.0.50 + 0x1a7e45)
#16 0x00000000005a7df1 Ffuncall (emacs-28.0.50 + 0x1a7df1)
#17 0x00000000005a8430 Fapply (emacs-28.0.50 + 0x1a8430)
#18 0x00000000005ac2c0 Fcall_interactively (emacs-28.0.50 + 0x1ac2c0)
#19 0x00000000005a7df1 Ffuncall (emacs-28.0.50 + 0x1a7df1)
#20 0x00000000005e74f1 exec_byte_code (emacs-28.0.50 + 0x1e74f1)
#21 0x00000000005a7d25 Ffuncall (emacs-28.0.50 + 0x1a7d25)
#22 0x000000000052e508 command_loop_1 (emacs-28.0.50 + 0x12e508)
#23 0x00000000005a4c47 internal_condition_case (emacs-28.0.50 + 0x1a4c47)
#24 0x0000000000520fe4 command_loop_2 (emacs-28.0.50 + 0x120fe4)
#25 0x00000000005a725b internal_catch (emacs-28.0.50 + 0x1a725b)
#26 0x0000000000524cd3 command_loop (emacs-28.0.50 + 0x124cd3)
#27 0x000000000065031f recursive_edit_1.isra.0 (emacs-28.0.50 + 0x25031f)
#28 0x0000000000525076 Frecursive_edit (emacs-28.0.50 + 0x125076)
#29 0x0000000000431090 main (emacs-28.0.50 + 0x31090)
#30 0x00007f283aaf11e2 __libc_start_main (libc.so.6 + 0x281e2)
#31 0x000000000043320e _start (emacs-28.0.50 + 0x3320e)
Stack trace of thread 174374:
#0 0x00007f283abbfa5f __poll (libc.so.6 + 0xf6a5f)
#1 0x00007f28413bea36 g_main_context_iterate.constprop.0 (libglib-2.0.so.0 + 0xa5a36)
#2 0x00007f284136c163 g_main_loop_run (libglib-2.0.so.0 + 0x53163)
#3 0x00007f28415b501a gdbus_shared_thread_func.lto_priv.0 (libgio-2.0.so.0 + 0x11001a)
#4 0x00007f284139a402 g_thread_proxy (libglib-2.0.so.0 + 0x81402)
#5 0x00007f283ae873f9 start_thread (libpthread.so.0 + 0x93f9)
#6 0x00007f283abcab53 __clone (libc.so.6 + 0x101b53)
Stack trace of thread 174373:
#0 0x00007f283abbfa5f __poll (libc.so.6 + 0xf6a5f)
#1 0x00007f28413bea36 g_main_context_iterate.constprop.0 (libglib-2.0.so.0 + 0xa5a36)
#2 0x00007f2841369e73 g_main_context_iteration (libglib-2.0.so.0 + 0x50e73)
#3 0x00007f2827b1864d dconf_gdbus_worker_thread (libdconfsettings.so + 0x664d)
#4 0x00007f284139a402 g_thread_proxy (libglib-2.0.so.0 + 0x81402)
#5 0x00007f283ae873f9 start_thread (libpthread.so.0 + 0x93f9)
#6 0x00007f283abcab53 __clone (libc.so.6 + 0x101b53)
Stack trace of thread 174372:
#0 0x00007f283abbfa5f __poll (libc.so.6 + 0xf6a5f)
#1 0x00007f28413bea36 g_main_context_iterate.constprop.0 (libglib-2.0.so.0 + 0xa5a36)
#2 0x00007f2841369e73 g_main_context_iteration (libglib-2.0.so.0 + 0x50e73)
#3 0x00007f284136ba91 glib_worker_main (libglib-2.0.so.0 + 0x52a91)
#4 0x00007f284139a402 g_thread_proxy (libglib-2.0.so.0 + 0x81402)
#5 0x00007f283ae873f9 start_thread (libpthread.so.0 + 0x93f9)
#6 0x00007f283abcab53 __clone (libc.so.6 + 0x101b53)
In data mercoled? 14 aprile 2021 17:54:45 CEST, Gregory Heytings ha scritto:
>
> >> The crash occur when switching from one buffer to others using
> >> counsel-switch-buffer (via minibuffer). I'm wasn't doing anything
> >> special, in *scratch* buffer I was trying to figure out how to properly
> >> use fontset functions.
> >
> > Could you provide a backtrace? See `C-h C-d' for information on how to
> > do that.
> >
> > Could you provide a recipe for reproducing it, starting from "emacs -Q"?
> >
>
> This looks like yet another occurrence of bug#47207.
>
next prev parent reply other threads:[~2021-04-14 19:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-14 10:12 bug#47774: 28.0.50; crash when using minibuffer Vincenzo Pupillo
2021-04-14 14:39 ` Stefan Kangas
2021-04-14 15:54 ` Gregory Heytings
2021-04-14 19:37 ` Vincenzo Pupillo [this message]
2021-04-15 8:52 ` Vincenzo Pupillo
2021-04-16 13:25 ` Vincenzo Pupillo
2021-04-16 14:43 ` martin rudalics
2021-04-16 15:31 ` Vincenzo Pupillo
2021-04-14 14:47 ` Eli Zaretskii
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=2196410.ElGaqSPkdT@localhost.localdomain \
--to=v.pupillo@gmail.com \
--cc=47774@debbugs.gnu.org \
--cc=gregory@heytings.org \
--cc=stefan@marxist.se \
/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.