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:mime-version:content-type
	:content-transfer-encoding:date:from:to:subject:in-reply-to
	:references:message-id; q=dns; s=default; b=VP1FaZVztnObnm63Gd+t
	Du86S12FLwlUU/LM88oXHFD3LO5TZJhMDGK9Ao6v444IusBuQmVeUK4DSWzsMISc
	ys5pmfC4kq6OOZl+ibf20oZ+qxspoUVjutN1+X6pSJEkElXaKaQsHDL/Imv2E+9/
	mQLo3GkqjGrCcDGGH0VweVE=
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:mime-version:content-type
	:content-transfer-encoding:date:from:to:subject:in-reply-to
	:references:message-id; s=default; bh=2rZ3NlYct/f2+MYU7rUkZu+bzb
	8=; b=K4ODPg/7OlGR+j8B9gVBZGBS+1u1ideWyxcs5dCFdG1V4LjVXlwJfb8H1e
	22QO4RsHyo5v3eoaOUYKdJL7I0lzaMa0dr+zb4h+Yhb/cfgv81CvpGeZNNjarVo8
	Mnzxo9PZydV2LvmLnIl1Gu2ZgR1jzFu22qUgPDpPrjusfEC24=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=3.6 required=5.0 tests=AWL,BAYES_60,KAM_STOCKTIP,RDNS_NONE,SPF_HELO_PASS,URIBL_BLOCKED autolearn=no version=3.3.2
X-HELO: smtprelay06.ispgateway.de
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Date: Wed, 04 Dec 2013 09:09:53 +0100
From: Markus Hoenicka <markus DOT hoenicka AT mhoenicka DOT de>
To: cygwin AT cygwin DOT com
Subject: Re: Please try newest snapshot (was Re: emacs-x11: new clipboard size =?UTF-8?Q?limitation=3F=29?=
In-Reply-To: <20131203211058.GB6179@ednor.casa.cgf.cx>
References: <ac98a224051c2e59d2a1a0d455717531 AT mhoenicka DOT de> <529C8716 DOT 7020601 AT dronecode DOT org DOT uk> <20131202141740 DOT GC11800 AT calimero DOT vinschen DOT de> <529C9F81 DOT 5060900 AT dronecode DOT org DOT uk> <20131203103129 DOT GG11800 AT calimero DOT vinschen DOT de> <20131203112830 DOT GH11800 AT calimero DOT vinschen DOT de> <529E0D3B DOT 8020505 AT dronecode DOT org DOT uk> <20131203211058 DOT GB6179 AT ednor DOT casa DOT cgf DOT cx>
Message-ID: <6ee00a6f479331e762ef054420653c87@mhoenicka.de>
X-Sender: markus DOT hoenicka AT mhoenicka DOT de
User-Agent: Roundcube Webmail
X-Df-Sender: bWFya3VzLmhvZW5pY2thQG1ob2VuaWNrYS5kZQ==
X-IsSubscribed: yes

Am 2013-12-03 22:10, schrieb Christopher Faylor:
> On Tue, Dec 03, 2013 at 04:56:27PM +0000, Jon TURNEY wrote:
>> Tried bisecting through the X server versions for the past 6 months, 
>> and it
>> seems that this problem first appears in X server 1.14.3-2
>> 
>> (As an aside, it's probably relevant to the recent discussion, that I 
>> can't
>> find the thread for, about how many previous versions we should keep 
>> around
>> that it's not possible to do this bisection without 'Secret Knowledge' 
>> at the
>> moment)
>> 
>> This does contain a few clipboard changes, and in particular it 
>> changes the
>> way the messages get processed so we will return to the select() more 
>> often
>> (after each stage of the conversion operation), which it looks like it 
>> could
>> be incorrect sometimes, but I'd expect this to cause unneeded blocking
>> (waiting in select() for a message which has already been placed on 
>> the event
>> queue by XPending() rather than the observed behaviour.
>> 
>> Anyhow, I guess I need to look at this some more...
>> 
>>> Talking about wndproc.c, it only checks iReturn for being < 0.  After
>>> that, we don't really know which value it has, we only know that
>>> FD_ISSET(iConnNumber, &fdsRead) returns 0.  The value of iReturn 
>>> should
>>> be printed in the debug output at line 133.
>> 
>> It's 0 when I inspect it with the debugger, but yes, I'll change that.
>> 
>>> What kind of object is the iConnNumber descriptor?  Pipe?  Fifo?
>>> Socket?  /dev/windows?  We really need a simple testcase without the
>>> X and emacs overhead...
>> 
>> It's a socket connected to the X server.
> 
> I added an ugly hack to work around this symptom in the latest cygwin.
> It shouldn't have any big impact on anything but this particular
> scenario but I would appreciate it if people downloaded today's 
> snapshot
> and verified that things are still working ok.
> 
> I plan on addressing the actual problem for Cygwin 1.7.28.
> 

Hi,

the nightly snapshot does not seem to do me any good with regard to the 
clipboard problem. I performed the following test, and I hope this is 
what you had in mind:

- make sure all Cygwin processes have terminated
- rename /bin/cygwin1.dll to /bin/cygwin1.dll.backup
- copy the nightly snapshot of 2013-12-04 to /bin and rename it 
cygwin1.dll
- rename /bin/XWin.exe (the test version mentioned by Jon) to 
/bin/XWin.exe.test
- rename /bin/XWin.exe.backup (the stock version that came with my last 
update) to /bin/XWin.exe

A quick test shows that trying to copy approx. two printed pages worth 
of ASCII text from an Emacs buffer to LibreOffice Writer still triggers 
the clipboard failure.

If I revert the changes above, i.e. reactivate the stock cygwin1.dll 
(1.7.25) and Jon's XWin test version, the clipboard works again.

regards,
Markus




-- 
Markus Hoenicka
http://www.mhoenicka.de
AQ score 38


--
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