From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 56792-done@debbugs.gnu.org, David Welch <davidwelch158@hotmail.com>
Subject: bug#56792: 29.0.50; Emacs crashes when selecting text if xfreerdp is also running
Date: Thu, 28 Jul 2022 18:14:52 +0800 [thread overview]
Message-ID: <878rodr1b7.fsf@yahoo.com> (raw)
In-Reply-To: <87bkt9y3ia.fsf@gnus.org> (Lars Ingebrigtsen's message of "Thu, 28 Jul 2022 11:45:33 +0200")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text
> editors" <bug-gnu-emacs@gnu.org> writes:
>
>> The PGTK build does not support X11, so you should build without PGTK
>> enabled. This crash is known to happen there, and will not be fixed,
>> since adding 300-400 lines of X specific selection code to the PGTK port
>> seems very irrational for a platform that it is not intended to support.
>
> Emacs shouldn't segfault, though. It's fine to signal an error in this
> situation, but segfaulting is not.
The segfault (which is really not a segfault, just GDK displaying a
window system error and aborting in an unusual manner) is hard to avoid
without adding X specific error handling code
(gdk_x11_display_error_trap_push). Which will then add a dependency on
the X11-specific parts of GDK, and won't work if Emacs did not see them
at build-time.
next prev parent reply other threads:[~2022-07-28 10:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-27 13:35 bug#56792: 29.0.50; Emacs crashes when selecting text if xfreerdp is also running David Welch
2022-07-27 13:49 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-27 14:21 ` David Welch
2022-07-28 0:39 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-28 8:24 ` David Welch
2022-07-28 9:45 ` Lars Ingebrigtsen
2022-07-28 10:14 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-07-28 10:25 ` Lars Ingebrigtsen
2022-07-28 10:49 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=878rodr1b7.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=56792-done@debbugs.gnu.org \
--cc=davidwelch158@hotmail.com \
--cc=larsi@gnus.org \
--cc=luangruo@yahoo.com \
/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).