Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Content-class: urn:content-classes:message MIME-Version: 1.0 Subject: RE: 1.5.10: expr + configure failure + testcase (also on 1.5.11-1) Content-Type: text/plain; charset="us-ascii" Date: Tue, 14 Sep 2004 09:30:24 +0200 Message-ID: <90459864DAD67D43BDD3D517DEFC2F7D7115@axon.Axentia.local> X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Peter Ekberg" To: "Bogdan Vacaliuc" Cc: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id i8E7UaVi005687 Bogdan Vacaliuc wrote: > In your *new* trace there are the same trace (on line 176632) > in the 'zone' between the fork() and the parent-shell exit decision > point of your most recent trace. > > Did you update your cygwin since your last run? Perhaps its > just an artifact? The set happens 4 times in your trace: Yes, the new trace is with cygwin1.dll 1.5.11-1, the old one was with 1.5.10-3, sorry if I didn't mention that... Cheers, Peter -- 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/