From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23118 invoked by alias); 15 Apr 2005 20:50:35 -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 23098 invoked from network); 15 Apr 2005 20:50:32 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org with SMTP; 15 Apr 2005 20:50:32 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.11/8.12.11) with ESMTP id j3FKoWNM020667 for ; Fri, 15 Apr 2005 16:50:32 -0400 Received: from pobox.corp.redhat.com (pobox.corp.redhat.com [172.16.52.156]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id j3FKoWO12821; Fri, 15 Apr 2005 16:50:32 -0400 Received: from localhost.localdomain (sebastian-int.corp.redhat.com [172.16.52.221]) by pobox.corp.redhat.com (8.12.8/8.12.8) with ESMTP id j3FKoVjs010628; Fri, 15 Apr 2005 16:50:31 -0400 Subject: Re: strange behaviour -- gdbtk & stdin on winxp From: Keith Seitz To: James Lemke Cc: gdb@sources.redhat.com In-Reply-To: <1113597409.18830.311.camel@keel.thelemkes.ca> References: <1113597409.18830.311.camel@keel.thelemkes.ca> Content-Type: text/plain Date: Fri, 15 Apr 2005 20:50:00 -0000 Message-Id: <1113598230.4459.2.camel@lindt.uglyboxes.com> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-SW-Source: 2005-04/txt/msg00106.txt.bz2 On Fri, 2005-04-15 at 16:36 -0400, James Lemke wrote: > All works as expected with xscale-elf-gdb or xscale-elf-insight -nw. > But with the GUI, fgets() returns immediately with NULL, and errno set > to 9 (EBADF). > > When built for a Linux host, xscale-elf-insight with and without -nw > work fine. I am assuming that you're trying to run on windows, and your problem doesn't surprise me in the least. Quite frankly, I don't think we ever got windows working as well as unix hosts. While I would guess this works for native cygwin apps, I'll bet insight never gets stdin reopened for some "terminal", and I don't believe that there is any special magic in gdb/insight to re-route stdin calls to the console window (although on a remote that shouldn't be too hard). I suspect some hacking is in your future... Keith