On Jun 17 14:54, Corinna Vinschen wrote: > On Jun 17 12:16, Corinna Vinschen wrote: > > On Jun 14 23:15, Jeremy Hetzler wrote: > > > After some testing, the limit seems to be 64k. It only happens when > > > reading data that was copied to the clipboard by a Windows program (in > > > this case Excel). > > > [...] > > > 583 $ cat /dev/clipboard >out.cat > > > cat: /dev/clipboard: Bad address > > > [...] > > > Does that help? > > > > Yes, thank you. There was an ill-conceived check for the last character > > in the buffer being a high surrogate UTF-16 character. It worked only > > if the clipboard content was small enough to fit into a single read of > > the application. If it was too big, and the application had to call > > read again to fetch more from the clipboard, it tried to read the > > character beyond the array boundary. I fixed that in CVS. I'll probably > > create a new developer snapshot and a 64 bit test version later today. > > FYI, I'm just uploading a new developer snapshot 2013-06-17 to > http://cygwin.com/snapshots/, as well as a new 64 bit Cygwin test > release 1.7.21-4. Please give one of them a try.
Guys? Ping? Any testers? Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat -- 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
