X-Spam-Check-By: sourceware.org Date: Mon, 4 Dec 2006 09:13:44 -0800 From: Yitzchak Scott-Thoennes To: cygwin@cygwin.com, andrew_certain_cygwin@thecertains.com Subject: Re: Problem with perl debugger and stdin Message-ID: <20061204171344.GA840@efn.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On Sat, Dec 02, 2006 at 02:25:24PM -0800, Andrew Certain wrote: > In a normal UNIX environment, you can run the perl debugger > and still redirect an input file to stdin. In other words, > > perl -d myscript < mydata > > does the right thing, namely, that you enter the debugger, the debugger > reads input from the keyboard, but if the script reads from STDIN, it gets > lines from mydata. > > Under cygwin, however, the same invocation causes the debugger to read > commands from mydata. There's probably something the debugger is doing for linux but not for cygwin because it thinks cygwin can't do it, but a quick scan of perl5db.pl didn't reveal it to me. Doing PERLDB_OPTS=TTY=/dev/tty perl -d ... should work, though. > Please include this line when replying. Is this some kind of behaviorist experiment? What's my prize? -- 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/