From: Ken Brown <kbrown@cornell.edu>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: fixup_mmaps_after_fork failure with cygwin-3.0.0
Date: Mon, 18 Feb 2019 14:32:00 -0000 [thread overview]
Message-ID: <16472397-2afd-dc23-e0b6-7a5069160b78@cornell.edu> (raw)
In-Reply-To: <20190218101009.GU4256@calimero.vinschen.de>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 2048 bytes --]
On 2/18/2019 5:10 AM, Corinna Vinschen wrote:
> On Feb 17 17:39, Corinna Vinschen wrote:
>> On Feb 17 16:34, Ken Brown wrote:
>>> On 2/17/2019 10:07 AM, Corinna Vinschen wrote:
>>>> On Feb 17 14:56, Ken Brown wrote:
>>>>> On 2/17/2019 4:13 AM, Corinna Vinschen wrote:
>>>>>>> If I may place a bet, please try to replace
>>>>>>> PROCESS_QUERY_LIMITED_INFORMATION with PROCESS_QUERY_INFORMATION
>>>>>
>>>>> That didn't change anything. Just to make sure I understood correctly, here's
>>>>> what I tried:
>>>>>
>>>>> --- a/winsup/cygwin/sigproc.cc
>>>>> +++ b/winsup/cygwin/sigproc.cc
>>>>> @@ -814,7 +814,7 @@ child_info::child_info (unsigned in_cb, child_info_types chtype,
>>>>> allow the child to copy cygheap etc. from the parent to itself. If
>>>>> we're forking, we also need handle duplicate access. */
>>>>> parent = NULL;
>>>>> - DWORD perms = PROCESS_QUERY_LIMITED_INFORMATION | PROCESS_VM_READ
>>>>> + DWORD perms = PROCESS_QUERY_INFORMATION | PROCESS_VM_READ
>>>>> | SYNCHRONIZE;
>>>>> if (type == _CH_FORK)
>>>>> {
>>>>>
>>>>>> On second thought, an even better candidate may be PROCESS_VM_OPERATION.
>>>>>
>>>>> That's even worse. With that change, simply invoking 'make' leads to
>>>>> the same error.
>>>>
>>>> PROCESS_VM_OPERATION has to be specified additionally, not replacing
>>>> PROCESS_QUERY_{LIMITED_}INFORMATION. Sorry if that wasn't clear.
>>>
>>> Success: Simply adding PROCESS_VM_OPERATION to the existing permissions fixes
>>> the problem.
>>
>> Thanks for tracking this down, I upload a fixed 3.0.1 pretty soon.
>
> Please try the today's developer snapshot from
> https://cygwin.com/snapshots/
Works fine so far. I've rebuilt emacs on both 64-bit and 32-bit with no problems.
Ken
\x03BKCB\x1cØ\x19[H\x1c\^[Ü\x1cÎ\b\b\b\b\b\b\x1a\x1d\x1d\x1c\x0eËØÞYÝÚ[ÛÛKÜ\x1cØ\x19[\Ë\x1d^[[\x03BTN\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\x1a\x1d\x1d\x1c\x0eËØÞYÝÚ[ÛÛKÙ\KÃB^[ØÝ[Y[\x18]\x1a[Û\b\b\b\b\b\b\b\b\x1a\x1d\x1d\x1c\x0eËØÞYÝÚ[ÛÛKÙ^[ØÜË\x1d^[[\x03B[ÝXØÜXH\x1a[Î\b\b\b\b\b\x1a\x1d\x1d\x1c\x0eËØÞYÝÚ[ÛÛKÛ[\vÈÝ[ÝXØÜXK\Ú[\^[\x19CBB
next prev parent reply other threads:[~2019-02-18 14:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-17 9:08 Ken Brown
2019-02-17 9:13 ` Corinna Vinschen
2019-02-17 9:32 ` Corinna Vinschen
2019-02-17 15:07 ` Ken Brown
2019-02-17 15:08 ` Corinna Vinschen
2019-02-17 16:40 ` Ken Brown
2019-02-17 16:42 ` Corinna Vinschen
2019-02-18 10:11 ` Corinna Vinschen
2019-02-18 14:32 ` Ken Brown [this message]
2019-02-18 14:32 ` Corinna Vinschen
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=16472397-2afd-dc23-e0b6-7a5069160b78@cornell.edu \
--to=kbrown@cornell.edu \
--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).