X-Recipient: archive-cygwin AT delorie DOT com X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 487333858D28 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=maxrnd.com Authentication-Results: sourceware.org; spf=none smtp.mailfrom=maxrnd.com Subject: Re: [ANNOUNCEMENT] Updated: cygutils 1.4.16-8 (Test) To: The Cygwin Mailing List References: <95DF7281-9391-4AEE-9427-7351DA47DBDE AT Denis-Excoffier DOT org> <2f219874-accb-5c79-d513-ccc0902f88fe AT maxrnd DOT com> From: Mark Geisert Message-ID: <5bda8193-b333-482e-6a19-3d48d5d6fe49@maxrnd.com> Date: Tue, 23 Nov 2021 01:08:01 -0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.4 MIME-Version: 1.0 In-Reply-To: X-Spam-Status: No, score=-4.7 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, KAM_LAZY_DOMAIN_SECURITY, NICE_REPLY_A, SPF_HELO_NONE, SPF_NONE, TXREP autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) 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: , Content-Type: text/plain; charset="utf-8"; Format="flowed" Errors-To: cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com Sender: "Cygwin" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by delorie.com id 1AN98NA1007444 Jon Turney wrote: > On 21/11/2021 10:36, Mark Geisert wrote: >> Hi Denis, >> >> Denis Excoffier wrote: >>> Hello, >>> >>>> On 2021-11-03 10:59, Mark Geisert wrote: >>>> >>>> The following packages have been uploaded to the Cygwin distribution: >>>> >>>> * cygutils-1.4.16-8 >>>> * cygutils-extra-1.4.16-8 >>>> * cygutils-x11-1.4.16-8 >>> >>> >>> The '-u' or '-d' option of getclip does not seem to work properly under xterm. >>> How to reproduce: >>> 1) Open an xterm >>> 2) Select a simple piece of text (with no line ending) >>> 3) getclip -u >>> 4) Observe 'Segmentation fault(core dumped)' >>> >>> If step 2 is replaced by ‘printf AAAA | putclip', no error. >>> If step 3 is replaced by ‘getclip’, no error. >>> >>> I can’t tell whether this is new or not. >> >> It appears to be old.  An xterm selection is placed on the Windows clipboard in >> CF_UNICODETEXT format.  'getclip' can deal with this, 'getclip -u' and 'getclip >> -d' cannot; they always request CF_TEXT (i.e., ANSI) format and assume they get >> a buffer of data.  But the formats don't match and there's no data supplied. >> That's why the segfault occurs. > > Odd... I think that Windows should convert CF_UNICODETEXT to CF_TEXT if needed > > See > https://docs.microsoft.com/en-gb/windows/win32/dataxchg/clipboard-formats#synthesized-clipboard-formats I did notice that doc when I was updating getclip and putclip. I wondered why that conversion didn't seem to be happening in the testcases and whether that was a Windows change over time. I had no answer. What surprised me about the segfault was that GetClipboardData(CF_TEXT) was returning zero, the error indication, but a subsequent GetLastError() returned zero as well, so no specific error. ..mark -- 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