public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Mark Geisert <mark@maxrnd.com>
To: cygwin@cygwin.com
Subject: Re: Incompatible clipboard format between 32bit and 64bit cygwin
Date: Sun, 26 Sep 2021 02:50:58 -0700	[thread overview]
Message-ID: <584f536c-b108-b562-b940-798ec2847c68@maxrnd.com> (raw)
In-Reply-To: <20210926103325.5c17eb11c3c8a56c377199a8@nifty.ne.jp>

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 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.  So getclip and 
putclip will need fixing as well.

I will submit a Cygwin patch to fix /dev/clipboard usage and a similar patch to 
cygutils for the utilities.

I appreciate your help in uncovering and investigating bugs in clipboard support.
Thanks & Regards,

..mark

  reply	other threads:[~2021-09-26  9:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-26  1:33 Takashi Yano
2021-09-26  9:50 ` Mark Geisert [this message]
2021-09-26 18:37   ` Thomas Wolff
2021-09-26 18:41     ` Thomas Wolff
2021-09-26 19:09       ` Lee
2021-09-26 20:46         ` Brian Inglis
2021-09-28  4:49       ` Mark Geisert
2021-09-28  5:22         ` Brian Inglis
2021-09-28  6:19           ` Takashi Yano
2021-09-28  6:46             ` Brian Inglis
2021-09-28  8:13               ` Takashi Yano
2021-09-28 17:11           ` Mark Geisert

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=584f536c-b108-b562-b940-798ec2847c68@maxrnd.com \
    --to=mark@maxrnd.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).