From: Thomas Wolff <towo@towo.net>
To: cygwin@cygwin.com
Subject: Re: /dev/clipboard corrupted
Date: Fri, 29 Jun 2012 09:47:00 -0000 [thread overview]
Message-ID: <4FED79A6.6050401@towo.net> (raw)
In-Reply-To: <1286377403.634959.1340961856516.JavaMail.open-xchange@email.1und1.de>
[-- Attachment #1: Type: text/plain, Size: 1924 bytes --]
On 29.06.2012 11:24, Corinna Vinschen wrote:
> On Jun 28 20:33, Thomas Wolff wrote:
>> Am 28.06.2012 10:20, schrieb Corinna Vinschen:
>>> On Jun 28 00:16, Thomas Wolff wrote:
>>>> If the clipboard contains large data, the contents retrieved from
>>>> /dev/clipboard gets corrupted.
>>>> I compared the following in a few cases:
>>>> * cat /dev/clipboard or cp /dev/clipboard (which are equal)
>>>> * mouse-paste into mintty, read with cat
>>>> * read /dev/clipboard within application
>>>>
>>>> and I found all three results to be different, the correct one
>>>> sometimes being cat /dev/clipboard but not always.
>>>> In today's case, the differences occured at byte 10240 and 65536
>>>> respectively, thus 10K-1 bytes or 64K-1 bytes being equal.
>>> I can't reprocude this. There's also nothing in the /dev/clipboard
>>> code which would rely on a 10K buffer or so. 64K, yes. But still,
>>> I tried with wordpad, vi, mintty, cat, and cp with a text file of
>>> about 90K. No problems. Do you have any reproducible testcase?
>> Not really reproducible (maybe later) but some more observations.
>> I made a small test program to read /dev/clipboard directly with
>> different buffer sizes.
> You know, we just love STCs. Send you small test program here, plus a
> short instruction how you created the clipboard content and how to call
> the testcase to see the problem.
Sure, so here it is. Open clipboard.txt with notepad, ^A^C to copy all,
then run the program to see bytes skipped.
Actually it seems to skip as many bytes per read() as there were
additional UTF-8 bytes (more bytes than characters) in the preceding
read block.
Checking the code again, variable pos seems to be used both as an index
into the clipboard (WCHAR) and an offset to the resulting string length
(char) which would explain the effect (not having checked all the
details though as I'm not familiar with the used APIs).
------
Thomas
[-- Attachment #2: clipboard.txt --]
[-- Type: text/plain, Size: 358 bytes --]
Scoloplos ist euryök. Er ist in der gesamten borealen Region in fast
allen marinen Sedimenten zu finden, die einen sandigen Anteil aufweisen.
Man findet ihn von Grönland bis zum Mittelmeer, in der Nordsee, an der
kanadischen Küste und im WeiÃen Meer (Markelova 1981).
Er besiedelt sowohl das «Eulitoral» als auch das âBathyalâ.
[-- Attachment #3: rcb.c --]
[-- Type: text/plain, Size: 687 bytes --]
#include <fcntl.h>
#include <stdio.h>
#include <stdlib.h>
int
main (int argc, char * * argv)
{
char * fn = "/dev/clipboard";
int fd = open (fn, O_RDONLY | O_BINARY, 0);
if (fd < 0) {
exit (fd);
}
int out_tty = isatty (1);
int filebuflen = 100;
argc --;
if (argc > 0) {
int ret = sscanf (argv [1], "%d", & filebuflen);
}
fprintf (stderr, "filebuflen %d\n", filebuflen);
char * filebuf = malloc (filebuflen + 1);
int n;
do {
n = read (fd, filebuf, filebuflen);
if (out_tty) {
filebuf [n] = 0;
printf ("read %d bytes: <%s>\n", n, filebuf);
} else {
fprintf (stderr, "read %d bytes\n", n);
write (1, filebuf, n);
}
} while (n > 0);
close (fd);
}
[-- Attachment #4: Type: text/plain, Size: 218 bytes --]
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next parent reply other threads:[~2012-06-29 9:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1286377403.634959.1340961856516.JavaMail.open-xchange@email.1und1.de>
2012-06-29 9:47 ` Thomas Wolff [this message]
2012-07-02 20:40 ` Corinna Vinschen
2012-06-27 22:16 Thomas Wolff
2012-06-28 8:04 ` Andy Koppe
2012-06-28 8:21 ` Corinna Vinschen
2012-06-28 18:33 ` Thomas Wolff
2012-06-29 7:24 ` 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=4FED79A6.6050401@towo.net \
--to=towo@towo.net \
--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).