From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: Ken Brown <kbrown@cornell.edu>
Cc: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: Fork issue with timerfd
Date: Mon, 25 Feb 2019 10:51:00 -0000 [thread overview]
Message-ID: <20190225100300.GH4133@calimero.vinschen.de> (raw)
In-Reply-To: <3142aff3-c7c3-187f-233e-089c5dc15ea2@cornell.edu>
[-- Attachment #1: Type: text/plain, Size: 1912 bytes --]
On Feb 25 03:21, Ken Brown wrote:
> On 2/24/2019 9:23 PM, Ken Brown wrote:
> > On 2/24/2019 2:52 PM, Corinna Vinschen wrote:
> >> On Feb 24 20:09, Corinna Vinschen wrote:
> >>> On Feb 24 19:55, Corinna Vinschen wrote:
> >>>> On Feb 24 17:27, Ken Brown wrote:
> >>>>> I'm seeing sporadic errors like this on 64-bit Cygwin when I first start emacs:
> >>>>>
> >>>>> 0 [main] emacs-X11 864 C:\cygwin64\bin\emacs-X11.exe: *** fatal error in
> >>>>> forked process - Can't recreate shared timerfd section during fork!
> >>>>> 0 [main] emacs 860 dofork: child 864 - died waiting for dll loading, errno 11
> >>>>>
> >>>>> If I exit and restart, everything will be fine almost every time.
> >>>>
> >>>> I think I see where the thinko was here. Can you try this?
> >>>
> >>> No, better try this:
> >>> [...]
> >>
> >> Even if this doesn't fully fix your problem, the patch itself is
> >> certainly better than the former code, so I pushed it. I also
> >> uploaded new developer snapshots to https://cygwin.com/snapshots/
> >> for testing.
> >
> > It's better, but not completely fixed. At the moment I'm testing 32-bit only,
> > since that was the only arch on which I could produce the problem reliably.
> > Previously I got the error every time I ran emacs. I just tried 5 times with
> > the new snapshot and only got the error twice.
>
> I withdraw that statement. After further tries, it's back to happening every time.
>
> > I'll work on this some more tomorrow and see if I can modify the emacs code so
> > that it gives me the full error message from Cygwin.
I had a late night inspiration, telling me that my timerfd
implementation has a design flaw in terms of fork/exec timer
sharing. I guess I should fix that first. Just ignore the
timerfd stuff for a bit, I'm working on that.
Sorry,
Corinna
--
Corinna Vinschen
Cygwin Maintainer
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-02-25 10:03 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 [this message]
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
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=20190225100300.GH4133@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin@cygwin.com \
--cc=kbrown@cornell.edu \
/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).