From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: "F. Romage" <mrfromage@comcast.net>
Cc: 62895@debbugs.gnu.org
Subject: bug#62895: Emacs 28.2 NS build segfaults on startup
Date: Wed, 19 Apr 2023 10:38:53 +0800 [thread overview]
Message-ID: <87leiofveq.fsf@yahoo.com> (raw)
In-Reply-To: <2101586494.3210530.1681682048060@connect.xfinity.com> (F. Romage's message of "Sun, 16 Apr 2023 17:54:08 -0400 (EDT)")
"F. Romage" <mrfromage@comcast.net> writes:
> Building Emacs 28.2 with the --with-ns option succeeds under Fedora 37 using GNUstep, but running it results in an immediate segmentation
> fault. I have attached the console messages before the segfault, as well as the strace output.
>
> With Emacs 27.2 the build runs and works for the most part, provided I use the cairo backend for GNUstep (defaults write NSGlobalDomain
> GSBackend libgnustep-cairo). With the default art backend or the xlib backend (libgnustep-art, libgnustep-xlib) the text in the editor is garbled
> and fairly unreadable. The cairo backend fixes all that, but it would be nice to use the default art backend, since many GNUstep apps work
> better with that.
The GNUstep build works in Emacs 29. Large parts of its font driver
have also been rewritten, so text display problems should no longer be
present.
next prev parent reply other threads:[~2023-04-19 2:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-16 21:54 bug#62895: Emacs 28.2 NS build segfaults on startup F. Romage
2023-04-19 2:38 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-04-20 2:18 ` F. Romage
2023-04-20 3:13 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-04-23 18:52 ` F. Romage
2023-04-24 0:47 ` 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=87leiofveq.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=62895@debbugs.gnu.org \
--cc=luangruo@yahoo.com \
--cc=mrfromage@comcast.net \
/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).