X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.6 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org From: Joe Crepeau To: "cygwin AT cygwin DOT com" Date: Fri, 30 Oct 2009 21:17:07 +0000 Subject: Redirecting stdin under gdb Message-ID: Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-ARA-Msg-ID: n9ULHBee004370 X-ARA-Bounce-Result: NO 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 Has the problem with redirecting stdin under gdb been fixed?=A0=20 The most recent posting I can find is from 1999 and it was a known problem = then. The problem is when you start up gdb and then type the following: run < input where "input" is an input file located in the current directory.=A0 gdb jus= t sits there, apparently waiting for input. According to the posting in 1999, the problem is because the "cmd arg parse= r in win32/gdb doesn't look for redirection symbols." If there is no fix, is there a work-around so that I can use gdb in cygwin? Thanks, Joe -- 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