From: Leo Prikler <leo.prikler@student.tugraz.at>
To: 42680@debbugs.gnu.org
Subject: [bug#42680] Fwd: Re: bug#42694: 26.3; Emacs crashes when linked against newer libx11
Date: Mon, 03 Aug 2020 16:51:14 +0200 [thread overview]
Message-ID: <d38723124f789cbbdee4c5834238b2dcb38a7bbb.camel@student.tugraz.at> (raw)
In-Reply-To: <20200802184655.30348-1-leo.prikler@student.tugraz.at>
[-- Attachment #1: Type: text/plain, Size: 95 bytes --]
It turns out, that this bug got fixed upstream independently using a
slightly different patch.
[-- Attachment #2: Weitergeleitete Nachricht – Re: bug#42694: 26.3; Emacs crashes when linked against newer libx11 --]
[-- Type: message/rfc822, Size: 3680 bytes --]
From: Eli Zaretskii <eliz@gnu.org>
To: Leo Prikler <leo.prikler@student.tugraz.at>
Cc: 42694@debbugs.gnu.org
Subject: Re: bug#42694: 26.3; Emacs crashes when linked against newer libx11
Date: Mon, 03 Aug 2020 17:40:41 +0300
Message-ID: <837dufbxna.fsf@gnu.org>
> From: Leo Prikler <leo.prikler@student.tugraz.at>
> Date: Mon, 03 Aug 2020 11:31:49 +0200
>
> Two days ago, a patch was sent to Guix updating libx11 to a newer
> version in order to fix CVE-2020-14344. This causes a segmentation
> fault in Emacs when trying to start an X window. After invoking GDB, I
> found the offending line to be:
>
> /* Determine XIC style */
> xic_style = best_xim_style (FRAME_X_XIM_STYLES (f));
>
> For some reason, FRAME_X_XIM_STYLES (f) returns NULL here and
> best_xim_style fails when ARRAYELTS is called on it. I've attached a
> patch, that checks for this case.
Thanks, this is bug#42676, which was solved yesterday.
prev parent reply other threads:[~2020-08-03 14:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <837dufbxna.fsf@gnu.org>
2020-08-02 18:46 ` [bug#42680] [PATCH] gnu: emacs: Ignore empty XIM styles Leo Prikler
2020-08-03 7:21 ` Mathieu Othacehe
2020-08-03 9:35 ` Leo Prikler
2020-08-03 10:40 ` bug#42680: " Mathieu Othacehe
2020-08-03 14:51 ` Leo Prikler [this message]
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d38723124f789cbbdee4c5834238b2dcb38a7bbb.camel@student.tugraz.at \
--to=leo.prikler@student.tugraz.at \
--cc=42680@debbugs.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/guix.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).