From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Error: child_copy: cygheap read copy failed.
Date: Fri, 20 Jan 2023 13:24:41 +0100 [thread overview]
Message-ID: <Y8qICZ6RSub4TJNG@calimero.vinschen.de> (raw)
In-Reply-To: <20230120211820.7e80fa2bf7332b351f3ba2a2@nifty.ne.jp>
On Jan 20 21:18, Takashi Yano via Cygwin wrote:
> On Fri, 20 Jan 2023 12:30:29 +0100
> Corinna Vinschen wrote:
> > Also, your ffplay executable isn't high-entropy-VA enabled, by any
> > chance?
>
> I'm sorry, but the high-entropy-va is ebabled.
>
> $ peflags -v /usr/bin/ff{mpeg,probe,play}
> /usr/bin/ffmpeg: coff(0x022e[+executable_image,+line_nums_stripped,+local_syms_stripped,+bigaddr,+sepdbg]) pe(0x8160[+high-entropy-va,+dynamicbase,+nxcompat,+tsaware])
> /usr/bin/ffprobe: coff(0x022e[+executable_image,+line_nums_stripped,+local_syms_stripped,+bigaddr,+sepdbg]) pe(0x8160[+high-entropy-va,+dynamicbase,+nxcompat,+tsaware])
> /usr/bin/ffplay: coff(0x022e[+executable_image,+line_nums_stripped,+local_syms_stripped,+bigaddr,+sepdbg]) pe(0x8160[+high-entropy-va,+dynamicbase,+nxcompat,+tsaware])
>
> peflags -e0 /usr/bin/ff{mpeg,probe,play} solves the issue.
> Thansk!
I'm glad to read that, actually!
> Shoud I remove dynamicbase flag as well?
I did a lot of local testing with ASLR locally, and it's fine for DLLs,
but not so much for the application executable itself.
You can keep dynamicbase for testing, but currently it's not advised
to do so, and you should definitely remove it for distro executables.
Thanks,
Corinna
next prev parent reply other threads:[~2023-01-20 12:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-20 3:56 Takashi Yano
2023-01-20 11:30 ` Corinna Vinschen
2023-01-20 12:18 ` Takashi Yano
2023-01-20 12:24 ` Corinna Vinschen [this message]
2023-01-20 12:26 ` Corinna Vinschen
2023-01-20 13:30 ` Takashi Yano
2023-01-20 15: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=Y8qICZ6RSub4TJNG@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--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).