From: Jan Synacek <jsynacek@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 30874@debbugs.gnu.org
Subject: bug#30874: 27.0.50; Emacs crashes
Date: Thu, 22 Mar 2018 14:05:26 +0100 [thread overview]
Message-ID: <CAPsXM8WJDeX+US110XtB=fP8noBQaNO8QE0KpYZn2GPViOs3SA@mail.gmail.com> (raw)
In-Reply-To: <83woy4i7rz.fsf@gnu.org>
On Thu, Mar 22, 2018 at 2:01 PM, Eli Zaretskii <eliz@gnu.org> wrote:
>> From: Jan Synacek <jsynacek@redhat.com>
>> Date: Thu, 22 Mar 2018 13:28:56 +0100
>> Cc: 30874@debbugs.gnu.org
>>
>> > Can you run this in X synchronous mode, so that we see which operation
>> > triggers the original X error? etc/DEBUG tells how to do that under
>> > "If you encounter X protocol errors".
>>
>> I tried the following but it doesn't work:
>>
>> gdb --args ./src/emacs -Q --eval='(setq x-command-line-resources
>> "emacs.synchronous: true")' --eval="(switch-to-buffer \"*scratch*\")"
>> --eval="(insert-char #x274c)" --eval="(set-fontset-font
>> \"fontset-default\" 'unicode \"Dejavu Sans Mono\")"
>> --eval="(debug-on-entry 'Fdelete_frame)"
>
> What about adding the -xrm "emacs.synchronous: true" switch to the
> Emacs invocation command -- does it also not work?
As far as I can tell, no. I still see the emacs frame remain open but
unresponsive and also see the same backtrace as before.
--
Jan Synacek
Software Engineer, Red Hat
next prev parent reply other threads:[~2018-03-22 13:05 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-20 10:24 bug#30874: 27.0.50; Emacs crashes Jan Synacek
2018-03-20 12:04 ` Eli Zaretskii
2018-03-20 12:12 ` Jan Synacek
2018-03-20 12:44 ` Eli Zaretskii
2018-03-22 12:28 ` Jan Synacek
2018-03-22 13:01 ` Eli Zaretskii
2018-03-22 13:05 ` Jan Synacek [this message]
2018-03-22 14:55 ` Eli Zaretskii
2018-03-26 9:12 ` Jan Synacek
2018-03-26 10:33 ` Robert Pluim
2018-03-26 15:25 ` Eli Zaretskii
2018-03-26 16:52 ` Robert Pluim
2018-03-26 17:33 ` Eli Zaretskii
2018-03-26 20:17 ` Robert Pluim
2018-03-26 22:16 ` Robert Pluim
2018-03-27 3:02 ` Eli Zaretskii
2018-03-27 8:57 ` Robert Pluim
2018-03-29 10:25 ` Eli Zaretskii
2018-03-29 16:14 ` Robert Pluim
2018-03-29 17:07 ` Eli Zaretskii
2018-03-30 5:10 ` Glenn Morris
2018-03-30 8:00 ` Eli Zaretskii
2018-03-30 10:36 ` Robert Pluim
2018-03-30 11:46 ` Eli Zaretskii
2018-03-30 13:00 ` Robert Pluim
2018-03-30 13:46 ` Eli Zaretskii
2018-03-31 13:55 ` Robert Pluim
2018-03-31 14:59 ` Eli Zaretskii
2018-04-03 9:24 ` Robert Pluim
2018-04-03 8:00 ` Jan Synacek
2018-04-03 9:22 ` Robert Pluim
2018-04-03 9:42 ` Eli Zaretskii
2018-04-03 12:52 ` Robert Pluim
2018-03-29 10:35 ` Jan Synacek
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='CAPsXM8WJDeX+US110XtB=fP8noBQaNO8QE0KpYZn2GPViOs3SA@mail.gmail.com' \
--to=jsynacek@redhat.com \
--cc=30874@debbugs.gnu.org \
--cc=eliz@gnu.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).