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:message-id:in-reply-to:references
	:subject:mime-version:content-type:content-transfer-encoding; q=
	dns; s=default; b=rcbqvV/+PTVqSpSJit2rwuiQWcCL+r+7dg+F130UBp2Qye
	tviaAu722LAQzrSKcAUoxZKj30xeV+46W7i2R0DL2hZaR0ieNkM9kFzm9Ol+DQ08
	9WhX/++oawVRGvJDI35gohkulgXr3GgdmJKbkwQg53c9vsoNdRNPXQLHJsPOw=
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:message-id:in-reply-to:references
	:subject:mime-version:content-type:content-transfer-encoding; s=
	default; bh=6QGU7BOuDSWlsATTB226gn0Z9ss=; b=r7e6IxsGGyrYwu5RGBMl
	G+NLvb3QkICC7okIEGRDw+1tvqixzZAKMQPyiPn/eKUi9kVysKZf/pc7P7PBpdLM
	VcwEfsPTtjLl1Up50Y0onrQVokRkJZwuyIqOD7zoZEzI+rEb4fhIc6xhXzZnwIOq
	LMfHnnqd+u31shey4US7CIU=
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=1.0 required=5.0 tests=BAYES_40,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_NONE autolearn=no version=3.3.2 spammy=H*MI:sk:44459aa, HImportance:Medium, H*M:465d, H*f:sk:44459aa
X-HELO:	mout.kundenserver.de
Date:	Thu, 26 May 2016 16:55:44 +0200 (CEST)
From:	Tobias Zawada <i_inbox AT tn-home DOT de>
To:	cygwin AT cygwin DOT com
Message-ID:	<1002567840.45243.3a1a3cbe-ee7e-465d-8585-9c4a96076936.open-xchange@email.1und1.de>
In-Reply-To:	<44459aa0-4381-2368-ab63-5dffc26f3344@cornell.edu>
References:	<466943424 DOT 37628 DOT 394d161a-7219-415d-a659-0f774811ad2d DOT open-xchange AT email DOT 1und1 DOT de> <44459aa0-4381-2368-ab63-5dffc26f3344 AT cornell DOT edu>
Subject:	Re: emacs gud-interface is not updated after gdb command execution (maybe because of incomplete output from gdb)
MIME-Version:	1.0
X-Originating-Client:	open-xchange-appsuite
X-UI-Out-Filterresults:	notjunk:1;V01:K0:fHNhLFOClYQ=:GFUinUxagMwvEUjCSBkV0V 2NTvY9TTcBdzPD23OJWYEtghH5coqVIbbbqDINbgg4x/nM3GinyoGxFqwUki7nr1O4wq4lx3S tGtAjdem7qPDyB6PpymO7NmTHW+adLp6NdOPkW0QNvwfOSJTrNzgPcynsjODJuRy+ExSK7Mjp mfNXoXZWx4E2KmDJ7jfAeJIDwZNO+8x13Kfhkgx+A4KOY3+MInM/BZ9NIfmdXC3/7j0V144gT yNUZizvB/mujQRUodXyhAhjGxZEF3V2EX78iRJIF4F0hda6OxccttbiULeJkSer6Y9ovDPNzh 8uWL6bS1WHd6iaqmvp21BRHOU9DJv6Pubs5cr6USVDmyzQG90YKbZtetTqz/HdnX1nvgurPLb aqu5Y+5gpi+uboTXdFgmY48w5jYSuJ8QkdxJ/OMBv+vhElGLFBegetE7878B3dcTEgrR16uUW XN13pg9fDsrbp9f56eD+O5Ugp96ZtOdcliWshgqDiebbPRJ6npzPmEQ+KRqSdnh5bpZnZ+GIh UfVFQp0lIefFQric4zIV/U6abYynvVreMg6z/Ef9H+OGOkyDr/mtNCztndUH8oGbe33+OygER h66gRzxrAB26WBrHSqermxBeNK4fZV9X3bFkDIof314NqZghaW6RzofUty9wt6ZC1efe8pqQe N2bAgQkaiGuxoOwjHSTB5b4noUz2S6GuFIS9Z+kfvZavAp9D/Lz4brCCpKNVesQIeFKL8uh78 wLiIDZB+58HYEj/H
X-IsSubscribed:	yes

Thanks, Ken for the following info:

> This looks like a bug I reported several years ago; it actually has 
> nothing to do with emacs:
> 
>  https://www.cygwin.com/ml/cygwin/2011-10/msg00445.html
> 
> It was fixed but then reappeared some months later:
> 
>  https://www.cygwin.com/ml/cygwin/2012-05/msg00049.html
> 
> It was fixed again but apparently is back. The test case from the 
> original report still exhibits the problem.

I had a look at the elisp-function gdb-send.

The command process-send-string is used there for sending commands to gdb.

Is it right that the problem manifests itself already there?

The doc of process-send-string says that this command may send the string
contents as separate bunches of data.

If the output is already incomplete because of the partitioned input through
process-send-string I see no way for a cygwin-specific workaround and we must
wait for a fix of gdb.

Do you know where I should report the bug?

Best regards,
Tobias

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

- Raw text -