This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Fork issue with timerfd

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.

+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Samples for the Waldorf Blofeld:

Problem reports:
Unsubscribe info:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]