From: Eli Zaretskii <eliz@gnu.org>
To: stefan-husmann@t-online.de
Cc: 34051@debbugs.gnu.org
Subject: bug#34051: 27.0.50; Emacs 27 from master segfaults
Date: Sat, 12 Jan 2019 18:15:07 +0200 [thread overview]
Message-ID: <834ladg8dw.fsf@gnu.org> (raw)
In-Reply-To: <87r2dhyj2q.fsf@frege.i-did-not-set--mail-host-address--so-tickle-me> (stefan-husmann@t-online.de)
> From: stefan-husmann@t-online.de
> Date: Sat, 12 Jan 2019 16:46:53 +0100
>
>
> Emacs segfaults immediately for me under Arch Linux 64 bit. This happens with commit
> a1b7a3f2a3957a399d6c3c7bcffa07ac67da82fc and upwards.
>
> Commit c342b26371480316024e1e5d63cd8b3f035dda69 works fine.
>
> With emacs -Q the segfault does not happen immediately, but it happened
> whe I tried to open this bug report.
>
> [haawda@frege ~]$ emacs
> X protocol error: BadMatch (invalid parameter attributes) on protocol request 139
> Fatal error 6: Aborted
Please run Emacs under a debugger, set x-synchronize to the value of
t, then reproduce the problem, and post the backtrace shown by GDB.
Thanks.
next prev parent reply other threads:[~2019-01-12 16:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-14 15:08 "X protocol error: BadMatch" on current master Yuri D'Elia
2019-01-14 16:12 ` Eli Zaretskii
2019-01-12 15:46 ` bug#34051: 27.0.50; Emacs 27 from master segfaults stefan-husmann
2019-01-12 16:15 ` Eli Zaretskii [this message]
[not found] ` <87sgxxwtbs.fsf@frege.i-did-not-set--mail-host-address--so-tickle-me>
2019-01-12 20:22 ` Eli Zaretskii
2019-01-13 11:20 ` Stefan Husmann
2019-01-13 15:24 ` Eli Zaretskii
2019-01-15 16:52 ` Alan Third
2019-01-16 21:22 ` bug#34051: "X protocol error: BadMatch" on current master Yuri D'Elia
2019-01-16 21:28 ` Yuri D'Elia
2019-01-17 13:36 ` Eli Zaretskii
2019-01-17 17:39 ` Alan Third
2019-01-17 17:44 ` Yuri D'Elia
2019-01-17 17:50 ` Alan Third
2019-01-17 0:18 ` bug#34051: 27.0.50; Emacs 27 from master segfaults Katsumi Yamaoka
2019-01-17 17:42 ` Alan Third
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=834ladg8dw.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=34051@debbugs.gnu.org \
--cc=stefan-husmann@t-online.de \
/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.