From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: emacs gud-interface is not updated after gdb command execution (maybe because of incomplete output from gdb)
Date: Thu, 26 May 2016 18:01:00 -0000 [thread overview]
Message-ID: <506dac42-346b-0007-d1b5-5ea0930f8838@cornell.edu> (raw)
In-Reply-To: <1002567840.45243.3a1a3cbe-ee7e-465d-8585-9c4a96076936.open-xchange@email.1und1.de>
On 5/26/2016 10:55 AM, Tobias Zawada wrote:
> 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.
I already wrote a test case (which was improved by cgf) in my original
bug report. As you can see from reading that old thread, the problem
*is* Cygwin specific and is provoked without partitioned input.
> Do you know where I should report the bug?
This email thread is the right place to report the bug.
Ken
--
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
next prev parent reply other threads:[~2016-05-26 15:48 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-26 12:32 Tobias Zawada
2016-05-26 15:48 ` William M. (Mike) Miller
2016-05-26 17:48 ` Ken Brown
2016-05-26 18:00 ` Tobias Zawada
2016-05-26 18:01 ` Ken Brown [this message]
2016-05-31 1:47 ` gdb pty problem [Was: emacs gud-interface is not updated after gdb command execution (maybe because of incomplete output from gdb)] Ken Brown
2016-05-31 9:35 ` Ken Brown
2016-05-31 22:41 ` Corinna Vinschen
2016-06-01 12:51 ` Ken Brown
2016-06-01 13:02 ` Ken Brown
2016-06-01 14:28 ` Corinna Vinschen
2016-06-01 14:29 ` Corinna Vinschen
2016-06-01 14:33 ` Ken Brown
2016-06-01 15:22 ` Ken Brown
2016-06-01 18:29 ` Corinna Vinschen
2016-06-01 19:05 ` Ken Brown
2016-06-01 19:54 ` Corinna Vinschen
2016-06-01 20:01 ` Ken Brown
2016-06-01 21:05 ` [GOLDSTAR] " Corinna Vinschen
2016-06-02 2:09 ` Andrew Schulman
2016-06-01 14:18 ` Corinna Vinschen
2016-06-06 10:12 ` Takashi Yano
2016-06-06 13:16 ` Corinna Vinschen
2016-06-07 13:14 ` Takashi Yano
2016-06-07 16:11 ` Corinna Vinschen
2016-06-06 14:01 ` Ken Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=506dac42-346b-0007-d1b5-5ea0930f8838@cornell.edu \
--to=kbrown@cornell.edu \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).