This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Fork issue with timerfd
- From: Achim Gratz <Stromeko at nexgo dot de>
- To: cygwin at cygwin dot com
- Date: Tue, 05 Mar 2019 20:15:32 +0100
- Subject: Re: Fork issue with timerfd
- References: <20190224190908.GB10574@calimero.vinschen.de> <20190224195255.GF4133@calimero.vinschen.de> <133d62b5-afd5-ae73-b950-7b50471e111e@cornell.edu> <3142aff3-c7c3-187f-233e-089c5dc15ea2@cornell.edu> <20190225100300.GH4133@calimero.vinschen.de> <20190225202050.GP4133@calimero.vinschen.de> <e2cae181-b96a-2ce0-34b8-f8a48714c828@cornell.edu> <20190226085730.GQ4133@calimero.vinschen.de> <20190226094838.GS4133@calimero.vinschen.de> <d367bf35-3c62-15e9-f292-ff709066ec4c@cornell.edu> <20190227161904.GC4133@calimero.vinschen.de> <79567e26-1232-f462-9867-a463da0be56f@cornell.edu> <877edeo6cq.fsf@Rainer.invalid> <32195809-e79e-934c-2176-b498a7b379a4@cornell.edu>
Ken Brown writes:
> On 3/4/2019 1:13 PM, Achim Gratz wrote:
>> 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
> them.
Sorry, I shouldn't have said timerfd, it was just related to another
piece of timer code. What I was talking about was this:
(1001)~ > uname -a
CYGWIN_NT-10.0-WOW DRSSA732 3.0.2s(0.338/5/3) 2019-03-03 11:25 i686 Cygwin
(1002)~ > emacs-w32 &
[1] 60
(1003)~ > 1 [main] emacs-w32 60 D:\Freeware\Cygwin32\bin\emacs-w32.exe: *** fatal error - CreateThread failed for itimer - 0x0<0x0>, Win32 error 8
bin/ emacs-w32.exe.stackdump*
(1003)~ > cat emacs-w32.exe.stackdump
Stack trace:
Frame Function Args
End of stack trace
[1] + Hangup emacs-w32
(1004)~ >
Anyway, the latest snapshot seemingly resolved that issue as well, I can
no longer reproduce it.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Samples for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldSamplesExtra
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple