X-Recipient: archive-cygwin AT delorie DOT com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org D500A385841D DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com; s=default; t=1674221476; bh=KVRHOOdZjQXinHlyzzbC1aVQD9lOD0qYxzJY6RS1j9w=; h=Date:To:Subject:In-Reply-To:References:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To: From; b=ndvg5axCytkc+Q2dmENJC2C96f3sURiotAijHCu2zw/8AsxSPyxaJzoDAH8u/aMdo HzQjnrqtjVL1AFztXcLzwST0Tn/RSSmEelxfL0yp3MIaEDNPRvdggaEYKSSNFGdnga Brmn7/QSB2XwsH+eUv/lYQoa/Wl48woVM9t6W318= X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org C56793858D1E DKIM-Filter: OpenDKIM Filter v2.10.3 conssluserg-05.nifty.com 30KDUaQF008980 X-Nifty-SrcIP: [220.150.135.41] Date: Fri, 20 Jan 2023 22:30:36 +0900 To: cygwin AT cygwin DOT com Subject: Re: Error: child_copy: cygheap read copy failed. Message-Id: <20230120223036.a47addc981aed0b58339e3d6@nifty.ne.jp> In-Reply-To: References: <20230120125633 DOT 05136d9ae091b097fc9f9cf5 AT nifty DOT ne DOT jp> <20230120211820 DOT 7e80fa2bf7332b351f3ba2a2 AT nifty DOT ne DOT jp> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.30; i686-pc-mingw32) Mime-Version: 1.0 X-Spam-Status: No, score=-4.4 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, NICE_REPLY_A, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org X-BeenThere: cygwin AT cygwin DOT com X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Takashi Yano via Cygwin Reply-To: Takashi Yano Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com Sender: "Cygwin" On Fri, 20 Jan 2023 13:26:20 +0100 Corinna Vinschen wrote: > 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]) > > Btw., how did this happen? The native Cygwin compiler/linker combo > usually doesn't set the dynamicbase and high-entropy-VA flags by > default... Perhaps this is because configure of ffmpeg explicitly has the following lines: check_ldflags -Wl,--nxcompat,--dynamicbase check_ldflags -Wl,--high-entropy-va # binutils 2.25 Removing these lines makes ff{mpeg,probe,play} disable both high-entropy-va and dynamicbase flags. -- Takashi Yano -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation: https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple