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 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Subject: RE: found possible suspect for characters out of order bug X-MimeOLE: Produced By Microsoft Exchange V6.0.4417.0 Date: Tue, 11 Sep 2001 14:16:51 +1000 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: found possible suspect for characters out of order bug Thread-Index: AcE6dDWjduUQaiAWQ6aXSR4KjhVOcQABB0FQ From: "Robert Collins" To: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id AAA25014 > -----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? Rob