Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Date: Wed, 27 Jun 2001 02:50:36 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: gdb run < file Message-ID: <20010627025036.B20160@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20010626 DOT 234402 DOT 21347360 DOT Takaaki DOT Ota AT am DOT sony DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <20010626.234402.21347360.Takaaki.Ota@am.sony.com>; from Takaaki.Ota@am.sony.com on Tue, Jun 26, 2001 at 11:44:02PM -0700 On Tue, Jun 26, 2001 at 11:44:02PM -0700, Tak Ota wrote: >I encountered a problem in gdb. > >(gdb) run < file > >does not change the process stdin to the file. Yep. That's a limitation in windows gdb. >I just started looking into gdb source code for the first time in my >left. For now I found top.c has command loop but the size of the code >is so overwhelming. So I thought reporting the incident first may >solve the problem way before I can find the cause and fix. No one is working on this, currently. If you can provide a fix it would be appreciated. I don't know of any easy way to get this functionality, though. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/