Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <40C1FC07.6060908@earthlink.net>
Date: Sat, 05 Jun 2004 11:59:51 -0500
From: Don McCarley <don DOT mccarley AT earthlink DOT net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Problem on Cygwin with gdb:  segy input can't be tty
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 8f40263a492d305e1153976827bb424c239a348a220c2609ca31e024084e31750b25fc68950d4c1a548b785378294e88350badd9bab72f9c350badd9bab72f9c


In trying to debug code with gdb, any program taking stdin on the 
command line complains that tty (keyboard) is already taken by gdb, so 
it can't use tty.  Is there a way that you can get the input data into 
the program other than stdin; or force it in with stdin?

Example of problem:
---
$ gdb suresamp
GNU gdb 2003-09-20-cvs (cygwin-special)
Copyright ...
.
.
(gdb) r < /home/work/tape01-1.su
Starting program: /usr/local/cwp/bin/suresamp.exe < /home/work/tape01-1.su

/usr/local/cwp/bin/suresamp: fgettr.c: segy input can't be tty

Program exited with code 01.
(gdb)
---

suresamp (and other programs that use stdin) works fine when not in 
debug (gdb) mode (because gdb isn't using tty).

This may be a cygwin only issue, as it works on a linux sun box.

Any help or ideas are appreciated,
Don McCarley


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/