From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15483 invoked by alias); 1 May 2006 17:05:18 -0000 Received: (qmail 15475 invoked by uid 22791); 1 May 2006 17:05:18 -0000 X-Spam-Check-By: sourceware.org Received: from nile.gnat.com (HELO nile.gnat.com) (205.232.38.5) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 01 May 2006 17:05:16 +0000 Received: from localhost (localhost [127.0.0.1]) by filtered-nile.gnat.com (Postfix) with ESMTP id D357A48CBDA for ; Mon, 1 May 2006 13:05:13 -0400 (EDT) Received: from nile.gnat.com ([127.0.0.1]) by localhost (nile.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 12041-01-5 for ; Mon, 1 May 2006 13:05:13 -0400 (EDT) Received: from takamaka.act-europe.fr (s142-179-108-108.bc.hsia.telus.net [142.179.108.108]) by nile.gnat.com (Postfix) with ESMTP id 8B14848CBD5 for ; Mon, 1 May 2006 13:05:13 -0400 (EDT) Received: by takamaka.act-europe.fr (Postfix, from userid 507) id F3D8147E7F; Mon, 1 May 2006 10:05:12 -0700 (PDT) Date: Mon, 01 May 2006 17:05:00 -0000 From: Joel Brobecker To: gdb@sources.redhat.com Subject: MinGW gdb run in non-DOS terminal Message-ID: <20060501170512.GD936@adacore.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2006-05/txt/msg00000.txt.bz2 Hello, Starting to experiment a bit with MinGW-hosted debuggers, I noticed that when it is run outside of the DOS window, the terminal handling is a bit strange. The most obvious issue is when the debugger prints an error: the actual printing on screen of the error message is delayed and only finally printed after the next GDB prompt. This happens when in a DOS window running cygwin bash, when ssh'ing from an xterm to the machine and then running GDB, or when running GDB from GPS, which opens a pseudo-tty (I think!) to GDB. On the other hand, it works great when run in a DOS window. Has anybody else seen this? Maybe there is a missing-flush issue somewhere... Or maybe there is a workaround I don't know about? Otherwise, I'll have a look at this next. Thanks, -- Joel