X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:date:from:to:subject:message-id:references :mime-version:content-type:in-reply-to; q=dns; s=default; b=ZUYh 1uNBE7CSoNrcDgMD/bsF1fp8LtR1nZatokYANt8TK08jDnlWerLCyeMa4+vEJMdf EpmIlzlCNX7e/b2eSg1ndPHicUBtvfRwqacYSMVReCgtBHaCt0EgWkCJanirMVK6 EnNH/p2Z2zYz7UKd61tzlZ33Oprg4eGPQspxBDo= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:date:from:to:subject:message-id:references :mime-version:content-type:in-reply-to; s=default; bh=lntfeZJ5u5 RhUHynkQE1oP5f4KM=; b=vxC/NGwNdRpN0Y//6R5HN2IaI53ewlvZwNY89MqeSv LnR73i2vVOBh/Iwz6u9rNkXL+rg8RF8ggVqCilCmLW7U3YVUscZxaclHClfjpBPF JVqw21gZtgFSWUfJh2uI0Au20QjBqy2uuiVYmQBN/scx9v1FJU5Ct6JcYFjXnREd M= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com X-Spam-SWARE-Status: No, score=-1.8 required=5.0 tests=AWL,BAYES_00,TW_YG autolearn=ham version=3.3.1 Date: Mon, 17 Jun 2013 12:16:33 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: getclip and cygutils and cygcheck Message-ID: <20130617101633.GC21191@calimero.vinschen.de> Mail-Followup-To: cygwin AT cygwin DOT com 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> <20130614091553 DOT GC4087 AT calimero DOT vinschen DOT de> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) On Jun 14 23:15, Jeremy Hetzler wrote: > 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). > > Steps: > - Open attached file in Excel > - Ctrl-a to select all, ctrl-c to copy to clipboard > - Then: > > 582 $ getclip >out.gc > > 583 $ cat /dev/clipboard >out.cat > cat: /dev/clipboard: Bad address > > 584 $ wc /dev/clipboard > wc: /dev/clipboard: Bad address > 400 13526 65536 /dev/clipboard > > 585 $ ls -la out* > -rw-r--r--+ 1 jhetzler Domain Users 65536 Jun 14 23:03 out.cat > -rw-r--r--+ 1 jhetzler Domain Users 73922 Jun 14 23:03 out.gc > > This is 1.7.20 on 64-bit Windows 7 and Excel 2013. > > 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. Thanks, 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