X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.3 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,SPF_NEUTRAL X-Spam-Check-By: sourceware.org Message-ID: <4EA48B80.2080205@cornell.edu> Date: Sun, 23 Oct 2011 17:47:44 -0400 From: Ken Brown User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1 MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: gdb problem References: <4EA329A3 DOT 30800 AT cornell DOT edu> <20111023190414 DOT GB13536 AT ednor DOT casa DOT cgf DOT cx> In-Reply-To: <20111023190414.GB13536@ednor.casa.cgf.cx> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes 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 On 10/23/2011 3:04 PM, Christopher Faylor wrote: > On Sat, Oct 22, 2011 at 04:37:55PM -0400, Ken Brown wrote: >> The attached testcase illustrates a problem with `gdb -i=mi'. I've >> tested both gdb 7.3.50-1 and 7.3.50-2, with cygwin 1.7.9 as well as with >> several recent snapshots (including 2011-10-22). >> >> Under some circumstances, if gdb -i=mi is started and given several >> input lines at once, it only prints part of the output before stopping. >> I've been able to reproduce this once in a while while working >> interactively (by copying and pasting the whole bunch of input lines); >> in this case one can press Return to get the rest of the output. But >> the problem happens consistently with the attached test case, which runs >> gdb in a subprocess. One has to kill the gdb process before the main >> program exits. >> >> The STC runs as expected on Linux. > > Thanks for the STC. I had to tweak it to actually see how it was supposed > to work on Linux since only a limited number of lines from the pty were > being output. I've included the revised test case below. > > I made a simple change to Cygwin which will probably cause subtle > problems somewhere down the line. At least for now it seems to make gdb > operate as expected. > > I'm building a new snapshot now. Thanks, that fixes it (as well as the emacs problem that originally led to this report). In case there are emacs users wondering what this is about, I've been testing emacs-24, which uses gdb -i=mi instead of the obsolete gdb --annotate=3 used by emacs-23. 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