From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: Fork issue with timerfd
Date: Tue, 05 Mar 2019 19:15:00 -0000 [thread overview]
Message-ID: <87lg1t8757.fsf@Rainer.invalid> (raw)
In-Reply-To: <32195809-e79e-934c-2176-b498a7b379a4@cornell.edu> (Ken Brown's message of "Mon, 4 Mar 2019 21:45:22 +0000")
[-- Attachment #1: Type: text/plain, Size: 797 bytes --]
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:
[-- Attachment #2: emacs-crash --]
[-- Type: text/plain, Size: 480 bytes --]
(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)~ >
[-- Attachment #3: Type: text/plain, Size: 285 bytes --]
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
[-- Attachment #4: Type: text/plain, Size: 219 bytes --]
--
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
next prev parent reply other threads:[~2019-03-05 19:15 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-24 18:55 Ken Brown
2019-02-24 19:01 ` Corinna Vinschen
2019-02-24 19:53 ` Corinna Vinschen
2019-02-24 23:42 ` Corinna Vinschen
2019-02-25 3:21 ` Ken Brown
2019-02-25 7:10 ` Ken Brown
2019-02-25 10:51 ` Corinna Vinschen
2019-02-25 22:01 ` Corinna Vinschen
2019-02-26 3:12 ` Ken Brown
2019-02-26 9:01 ` Corinna Vinschen
2019-02-26 9:37 ` Corinna Vinschen
2019-02-26 11:46 ` Corinna Vinschen
2019-02-26 15:05 ` Ken Brown
2019-02-27 16:24 ` Corinna Vinschen
2019-02-27 16:39 ` Ken Brown
2019-02-27 19:31 ` Corinna Vinschen
2019-03-04 18:13 ` Achim Gratz
2019-03-04 21:46 ` Ken Brown
2019-03-05 19:15 ` Achim Gratz [this message]
2019-03-06 20:55 Peter Kozich (UM)
2019-03-06 21:23 ` Corinna Vinschen
2019-03-08 19:56 ` Peter Kozich (UM)
2019-03-08 20:10 ` Rockefeller, Harry
2019-03-08 20:22 ` Corinna Vinschen
2019-03-08 21:27 ` Rockefeller, Harry
2019-03-09 15:38 ` Corinna Vinschen
2019-03-08 22:04 ` Ken Brown
2019-03-09 12:35 ` Ken Brown
2019-03-09 15:38 ` Corinna Vinschen
2019-03-09 18:48 ` Ken Brown
2019-03-09 19:08 ` Corinna Vinschen
2019-03-08 22:21 ` Peter Kozich (UM)
2019-03-08 22:44 ` Peter Kozich (UM)
2019-03-09 15:39 ` Corinna Vinschen
2019-03-11 18:25 ` Peter Kozich (UM)
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=87lg1t8757.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--cc=cygwin@cygwin.com \
/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).