From: Eli Zaretskii <eliz@gnu.org>
To: "Marc Wilhelm Küster" <marc@budabe.eu>
Cc: 31547@debbugs.gnu.org
Subject: bug#31547: 25.3; Core dump: g_main_context_prepare() called recursively from within a source's check() or prepare() member.
Date: Sat, 02 Jun 2018 19:39:40 +0300 [thread overview]
Message-ID: <8336y5dtwz.fsf@gnu.org> (raw)
In-Reply-To: <87o9gtf94s.wl-marc@budabe.eu> (message from Marc Wilhelm Küster on Sat, 02 Jun 2018 18:25:39 +0200)
> Date: Sat, 02 Jun 2018 18:25:39 +0200
> From: Marc Wilhelm Küster <marc@budabe.eu>
> Cc: 31547@debbugs.gnu.org
>
> in order to get a more meaningful backtrace I've compiled emacs 26.1 directly from its source (source directly downloaded from http://mirror.switch.ch/ftp/mirror/gnu/emacs/emacs-26.1.tar.xz)
>
> The crash remains fully reproducible. I attach you the backtraces. Of yourse, I'm at your disposal for any additional information you may need
Thanks.
If the crash is reproducible, can you give a step by step recipe,
starting from "emacs -Q", for reproducing it?
next prev parent reply other threads:[~2018-06-02 16:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-22 4:45 bug#31547: 25.3; Core dump: g_main_context_prepare() called recursively from within a source's check() or prepare() member marc
2018-05-22 16:34 ` Eli Zaretskii
2018-05-22 19:43 ` Marc Wilhelm Küster
2018-05-23 2:29 ` Eli Zaretskii
2018-05-23 5:10 ` Marc Wilhelm Küster
2018-05-23 15:18 ` Eli Zaretskii
2018-05-29 5:12 ` Marc Wilhelm Küster
2018-06-02 16:25 ` Marc Wilhelm Küster
2018-06-02 16:39 ` Eli Zaretskii [this message]
2018-06-02 17:05 ` Marc Wilhelm Küster
2018-06-02 19:23 ` Eli Zaretskii
[not found] ` <997a15cf-3015-2929-2da4-86187eb84c74@budabe.eu>
2018-06-04 16:22 ` Eli Zaretskii
2018-06-04 17:36 ` Robert Pluim
2018-06-04 19:03 ` Marc Wilhelm Küster
2018-06-04 19:14 ` Eli Zaretskii
2018-06-05 12:56 ` Robert Pluim
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=8336y5dtwz.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=31547@debbugs.gnu.org \
--cc=marc@budabe.eu \
/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.