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


In response to this one:

      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

      ....

      Anyway, the latest snapshot seemingly resolved that issue as
      well, I can no longer reproduce it.


Unfortunately, only seemingly. Factually, the issue persists. And I
don't have to do anything with emacs just shoot up, wait cca. 20
seconds and it inevitably crashes, and it does so in the foreground,
too: 

peter@D11934N ~
$ emacs .bash_history  &
[2] 489
[1]   Done                    emacs .bash_history

peter@D11934N ~
$       1 [main] emacs 489 C:\CygWin\bin\emacs-w32.exe: *** fatal error - 
CreateThread failed for pipesel - 0x0<0x0>, Win32 error 8

[2]+  Hangup                  emacs .bash_history

peter@D11934N ~
$ uname -a
CYGWIN_NT-6.1-WOW D11934N 3.0.2(0.338/5/3) 2019-03-05 19:01 i686 Cygwin

peter@D11934N ~
$ cat emacs-w32.exe.stackdump

peter@D11934N ~
$



It is not always pipesel, I have also seen itimer. The stackdump is
sometimes an empty file as above, sometimes the same as Achim's.


Isn't it possible to put back 2.11.2 in the archives until 3.0 is made
stable? By mistake I deleted my copy and cannot find it anywhere.


best regards,
P. K.


--
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


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