From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30196 invoked by alias); 4 Jan 2003 21:09:04 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 30189 invoked from network); 4 Jan 2003 21:09:04 -0000 Received: from unknown (HELO redhat.com) (66.30.22.225) by 209.249.29.67 with SMTP; 4 Jan 2003 21:09:04 -0000 Received: by redhat.com (Postfix, from userid 201) id 281761C10F; Sat, 4 Jan 2003 16:09:21 -0500 (EST) Date: Sat, 04 Jan 2003 21:09:00 -0000 From: Christopher Faylor To: gdb@sources.redhat.com Subject: Re: bug in gdb tty command on cygwin Message-ID: <20030104210921.GC23974@redhat.com> Reply-To: gdb@sources.redhat.com Mail-Followup-To: gdb@sources.redhat.com References: <20030104094405.6de9d597.steven.obrien2@ntlworld.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030104094405.6de9d597.steven.obrien2@ntlworld.com> User-Agent: Mutt/1.5.1i X-SW-Source: 2003-01/txt/msg00045.txt.bz2 [Reply-To set to gdb mailing list] On Sat, Jan 04, 2003 at 09:44:05AM +0000, Steven O'Brien wrote: >Hi >I submitted a patch to fix a bug in cygwin gdb to the gdb-patches list - >see: >http://sources.redhat.com/ml/gdb-patches/2002-12/msg00761.html > >However, this did not attract any response. What is the next step in >getting this patch into gdb? Patience? >With this patch I am able to build and run a fully functional anjuta IDE >on cygwin-xfree86. Without it anjuta's debugger will not work on cygwin. >I am sure that other X11 GUIs for gdb on cygwin would also benefit from >this patch. > >The patch moves one line of code in just one file that is only used in >the cygwin build; and code that is only invoked if the --tty option or >tty command are invoked. I saw your patch but since it invoked a "Huh?" response, it required some study. I don't see any correlation between your description of the problem and your proposed patch. I don't know why closing the tty later would cause the kind of problem you were talking about, so it isn't an obvious "plop it right in" kind of patch. cgf