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 0A0A23858C2C Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=SystematicSw.ab.ca Authentication-Results: sourceware.org; spf=none smtp.mailfrom=systematicsw.ab.ca X-Authority-Analysis: v=2.4 cv=SdyUytdu c=1 sm=1 tr=0 ts=6152a697 a=T+ovY1NZ+FAi/xYICV7Bgg==:117 a=T+ovY1NZ+FAi/xYICV7Bgg==:17 a=IkcTkHD0fZMA:10 a=kpN3U7V2zNN4vsHDIoUA:9 a=QEXdDO2ut3YA:10 Subject: Re: Incompatible clipboard format between 32bit and 64bit cygwin To: cygwin AT cygwin DOT com References: <20210926103325 DOT 5c17eb11c3c8a56c377199a8 AT nifty DOT ne DOT jp> <584f536c-b108-b562-b940-798ec2847c68 AT maxrnd DOT com> <0b13b9ac-583f-ab72-4202-f8b187946d93 AT towo DOT net> <498f0cfb-c6c1-cb61-2e88-fcb9ce61f4d4 AT maxrnd DOT com> From: Brian Inglis Organization: Systematic Software Message-ID: <731c8611-4ed2-29fd-0b9c-33e221d6451e@SystematicSw.ab.ca> Date: Mon, 27 Sep 2021 23:22:30 -0600 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.14.0 MIME-Version: 1.0 In-Reply-To: <498f0cfb-c6c1-cb61-2e88-fcb9ce61f4d4@maxrnd.com> Content-Language: en-CA X-CMAE-Envelope: MS4xfDeN3ZO/Xp7yqAX55VAe7VV5CjzuAtj/aUUxLhhdg7jWJ95ewXlUZi9P2FGlLSPCvKDocZ5RJrYbOj6iP7eVqFdrLnl3HvuEr5+WOjh7KfXfsPzUe8l1 aQj94QiBX3UpBJQsLUTA0BVRyyBbB8XAns0Ck7SmyKt4uEZDWipF+fKCMrjnAXJhHc8haC0OGnqoCVC+HiGtFceVQ+Xn0aGQvDA= X-Spam-Status: No, score=-1164.8 required=5.0 tests=BAYES_00, BODY_8BITS, KAM_DMARC_STATUS, KAM_LAZY_DOMAIN_SECURITY, NICE_REPLY_A, RCVD_IN_BARRACUDACENTRAL, RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H4, RCVD_IN_MSPIKE_WL, SPF_HELO_NONE, SPF_NONE, TXREP autolearn=no 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: , Reply-To: cygwin AT cygwin DOT com 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 18S5NAOr030178 On 2021-09-27 22:49, Mark Geisert wrote: > Hi Thomas, > > Thomas Wolff wrote: >> >> Am 26.09.2021 um 20:37 schrieb Thomas Wolff: >>> >>> Am 26.09.2021 um 11:50 schrieb Mark Geisert: >>>> Hi Takashi, >>>> >>>> Takashi Yano via Cygwin wrote: >>>>> I noticed that cygwin clipboard is not compatible >>>>> between 32bit and 64bit cygwin. >>>>> >>>>> If I run 'echo AAAAAAAA > /dev/clipboard' in 32bit cygwin, >>>>> and run 'cat /dev/clipboard' in 64bit cygwin, this result in >>>>> cat: /dev/clipboard: Bad address >>>>> >>>>> This is because the structure >>>>> typedef struct >>>>> { >>>>>    timestruc_t   timestamp; >>>>>    size_t    len; >>>>>    char      data[1]; >>>>> } cygcb_t; >>>>> defined in fhandler_clipboard.cc has different size. >>>>> >>>>> Is this the known issue? >>>> >>>> I doubt anybody has ever tried what you did. >>> I have and it failed; I just didn't find it important enough to >>> report it here... Thanks for the plan to fix it. >>> >>>> I have been testing getclip and putclip between 32- and 64-bit >>>> environments, but neglected to test Cygwin-internal clipboard format >>>> that prepends cygcb_t to the user-supplied data. >> As we're at it, what's the purpose of a cygwin-internal clipboard >> format at all? >> Copy/paste between 32bit/64bit mintty works; mintty uses Windows >> CF_UNICODETEXT clipboard format. > > The cygwin-internal clipboard format records a timestamp and content > length when Cygwin (or putclip) updates the clipboard contents.  This > allows 'stat' and fstat() to show something sensible for > /dev/clipboard.  The latter feature went into Cygwin 1.7.13. > > Other than that, not much difference to CF_UNICODETEXT ;-). Would it perhaps make sense to include struct stat with appropriate entries rather than a couple of adhoc members unrelated to much else? -- Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada This email may be disturbing to some readers as it contains too much technical detail. Reader discretion is advised. [Data in binary units and prefixes, physical quantities in SI.] -- 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