public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Ken Brown <kbrown@cornell.edu>
To: Jim Reisert AD1C <jjreisert@alum.mit.edu>
Cc: cygwin@cygwin.com
Subject: Re: GNU Emacs 28.0.50 crash (emacs-w32)
Date: Thu, 7 Oct 2021 10:53:16 -0400	[thread overview]
Message-ID: <9d469b42-c28d-6f91-4258-e48e834ba2a5@cornell.edu> (raw)
In-Reply-To: <CAK-n8j5jYHBQnv3XbNL=wW-whGvkNewRRtJBQ+bRmssu3y2mGw@mail.gmail.com>

On 10/7/2021 10:16 AM, Jim Reisert AD1C wrote:
>> Could this be the following problem that I mentioned in the release announcement?
>>
>>> Compilation is done asynchronously, with a log in a buffer called
>>> *Async-native-compile-log*.  If you run emacs-w32 and exit while a
>>> compilation is in progress, you might see a dialog box saying that
>>> emacs has aborted and asking if you want to attach a debugger.  Just
>>> say No.  If this annoys you, check the compilation buffer before
>>> exiting, and wait for the "Compilation finished" message.
>>
>> I'll add one more thing that I didn't know when I wrote that: You can customize
>> the variable native-comp-async-query-on-exit if you want to be warned that there
>> are compilations in process when you exit.
> 
> Sure, that could be the problem.  I'll try the workaround.

Thanks.  Please report back.

I'm about to announce a new test release that tries to work around the problem 
in a different way.  I'd be interested in hearing how that works too.

> I do notice that there are separate compilation directories for emacs
> and emacs-w32.  Is this necessary?

Yes.  Each build environment for emacs requires its own compiled libraries. 
Here "build environment" includes source files, system, and configuration 
options.  In this case, the build of emacs-w32 used the configuration option 
"--with-w32" that wasn't used in the build of emacs-X11.

Thanks very much for testing!

Ken

  reply	other threads:[~2021-10-07 14:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-06 14:22 Jim Reisert AD1C
2021-10-06 14:25 ` Jim Reisert AD1C
2021-10-06 15:38 ` Ken Brown
2021-10-06 15:47   ` Ken Brown
2021-10-07 14:16   ` Jim Reisert AD1C
2021-10-07 14:53     ` Ken Brown [this message]
2021-10-07 16:04       ` Jim Reisert AD1C
2021-10-07 20:21       ` Jim Reisert AD1C
2021-10-08 16:18         ` Ken Brown

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=9d469b42-c28d-6f91-4258-e48e834ba2a5@cornell.edu \
    --to=kbrown@cornell.edu \
    --cc=cygwin@cygwin.com \
    --cc=jjreisert@alum.mit.edu \
    /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.
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).