This is the mail archive of the
mailing list for the Cygwin project.
Re: Fork issue with timerfd
- From: Ken Brown <kbrown at cornell dot edu>
- To: "cygwin at cygwin dot com" <cygwin at cygwin dot com>
- Date: Mon, 4 Mar 2019 21:45:22 +0000
- Subject: Re: Fork issue with timerfd
- References: <20190224190908.GB10574@calimero.vinschen.de> <20190224195255.GF4133@calimero.vinschen.de> <email@example.com> <firstname.lastname@example.org> <20190225100300.GH4133@calimero.vinschen.de> <20190225202050.GP4133@calimero.vinschen.de> <email@example.com> <20190226085730.GQ4133@calimero.vinschen.de> <20190226094838.GS4133@calimero.vinschen.de> <firstname.lastname@example.org> <20190227161904.GC4133@calimero.vinschen.de> <email@example.com> <877edeo6cq.fsf@Rainer.invalid>
On 3/4/2019 1:13 PM, Achim Gratz wrote:
> Ken Brown writes:
>> I've been using emacs extensively on both x86 and x86_64 with the latest
>> snapshot, and I've had no further problems. I think 3.0.2 is ready to go.
> I consistently see that problem with the latest snapshot 20190303 when
> trying to save a changed document from emacs-w32. I didn't try
> emacs-X11 and emacs-nox doesn't exhibit the problem (or rarely enough
> that I got through the day without it ever occuring).
By "that problem" do you mean a fork failure? I don't think it could be related
to the timerfd issues unless you're using an emacs that you built yourself or
installed from my personal Cygwin repo. The emacs in the Cygwin distro was
built before Cygwin supported the timerfd functions and so it doesn't try to use