This is the mail archive of the
mailing list for the Cygwin project.
Re: getclip and cygutils and cygcheck
- From: Thomas Wolff <towo at towo dot net>
- To: cygwin at cygwin dot com
- Date: Sat, 15 Jun 2013 21:36:56 +0200
- Subject: Re: getclip and cygutils and cygcheck
- References: <0D835E9B9CD07F40A48423F80D3B5A7021C57FB3 at USA7109MB022 dot na dot xerox dot net> <0D835E9B9CD07F40A48423F80D3B5A7021C58055 at USA7109MB022 dot na dot xerox dot net> <51B8D19B dot 7080400 at towo dot net> <20130613095556 dot GA21638 at calimero dot vinschen dot de> <CAOh4nmk2_9CV_X9HrxJ=mLJ0dJ889Yn53zrrYuciaFN7Ft1_9Q at mail dot gmail dot com> <20130614091553 dot GC4087 at calimero dot vinschen dot de> <CAOh4nmkU4ydx1FTxcL11OV3sUG9Qdb1RnLjV-x7KwOVW34Kciw at mail dot gmail dot com>
Am 15.06.2013 05:15, schrieb Jeremy Hetzler:
This sounds pretty much like the same observation I made in
At that time, however, the problem was finally fixed, so (not yet having
checked again, sorry) could the old problem have crept in again somehow?
On Fri, Jun 14, 2013 at 5:15 AM, Corinna Vinschen wrote:
What's that size? I'm not aware of any size restriction in the current
/dev/clipboard code. Well, there's an allocation when writing to the
clipboard, but it's only restricted by the size of the largest available
memory block in the process VM, in theory.
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).
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple