unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "F. Romage" <mrfromage@comcast.net>
To: Po Lu <luangruo@yahoo.com>
Cc: 62895@debbugs.gnu.org
Subject: bug#62895: Emacs 28.2 NS build segfaults on startup
Date: Sun, 23 Apr 2023 14:52:17 -0400 (EDT)	[thread overview]
Message-ID: <1794261786.640101.1682275937763@connect.xfinity.com> (raw)
In-Reply-To: <87edoffdq3.fsf@yahoo.com>

> On 04/19/2023 11:13 PM Po Lu <luangruo@yahoo.com> wrote:
> Then would you please show a backtrace from the crash, and also tell
> which version of GNUstep you have installed?  It works for me.

I was using GNUstep base 1.24 and gui 0.24. Upgrading to base 1.28 and gui 0.29 fixed the problem with Emacs 30.0.50 not starting. In fact it's more stable than Emacs 27.2 with the older GNUstep I had been using. I'm still trying to get themes working properly, but everything else seems to work fine. Thanks for providing a reason for upgrading GNUstep, which I had been putting off for several years. I think this bug report can be closed.





  reply	other threads:[~2023-04-23 18:52 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
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 [this message]
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=1794261786.640101.1682275937763@connect.xfinity.com \
    --to=mrfromage@comcast.net \
    --cc=62895@debbugs.gnu.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).