Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com Date: Tue, 11 Sep 2001 00:32:45 -0400 From: Christopher Faylor To: cygwin-developers AT cygwin DOT com Subject: Re: found possible suspect for characters out of order bug Message-ID: <20010911003245.A26829@redhat.com> Reply-To: cygwin-developers AT cygwin DOT com Mail-Followup-To: cygwin-developers AT cygwin DOT com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.21i On Tue, Sep 11, 2001 at 02:16:51PM +1000, Robert Collins wrote: > > >> -----Original Message----- >> From: Christopher Faylor [mailto:cgf AT redhat DOT com] >> >> Sorry, no. This is just the read method for the console. It >> does detect >> if a signal has been hit and reacts appropriately, though. > >Oh. anyway to get strace to log to a file _and_ allow stdout to behave >normally then? > >or is this a case of printfbombing? (given that debugging isn't an >option in this case...) > >ie from cmd.exe >strace bash >strace.log >and have bash send it's output to the console, not strace.log? strace -ofile bash cgf