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: Wed, 27 Feb 2019 16:24:00 -0000 [thread overview]
Message-ID: <20190227161904.GC4133@calimero.vinschen.de> (raw)
In-Reply-To: <d367bf35-3c62-15e9-f292-ff709066ec4c@cornell.edu>
[-- Attachment #1: Type: text/plain, Size: 1204 bytes --]
On Feb 26 13:39, Ken Brown wrote:
> On 2/26/2019 4:48 AM, Corinna Vinschen wrote:
> > On Feb 26 09:57, Corinna Vinschen wrote:
> >> On Feb 26 00:01, Ken Brown wrote:
> >>> I did get the following, however, during one of the trials (while emacs was idle):
> >>>
> >>> 1 [main] emacs 246 C:\Users\kbrown\src\emacs\i686-emacs26\src\emacs.exe: ***
> >>> fatal error - CreateThread failed for pipesel - 0x0<0x0>, Win32 error 8
> >>
> >> It's hard to imagine how this is related. CreateThread fails due to
> >> memory problems?!? A timerfd does not use a lot of resources, just a
> >> 96 bytes struct on the cygheap, a single page shared memory region, and
> > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^'
> >
> > This was at least the intention, but I accidentally created a 64K
> > region. Fixed in git and new snapshort forthcoming.
>
> Looks good so far. I've been running emacs on x86 for about an hour, running
> lots of subprocesses, with no problems. I'll keep using it throughout the day.
Ken? Any news? If you're satisfied with the current state, I'd like
to push 3.0.2 out.
Thanks,
Corinna
--
Corinna Vinschen
Cygwin Maintainer
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-02-27 16:19 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 [this message]
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=20190227161904.GC4133@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).