X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=1.1 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org X-MXL-Hash: 4a8872087d400758-1ded48f61c18931b1caa4d256fadae92fce58209 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: 1.7.0-58 fixes fork crash in 1.7-compiled app running on 1.5 Date: Sun, 16 Aug 2009 13:54:30 -0700 Message-ID: From: "Martin Dorey" To: X-MAIL-FROM: X-AnalysisOut: [v=1.0 c=1 a=ZTuw4BgbB8gA:10 a=4m6HPYH2f5oGN3e34rXPbw==:17 ] X-AnalysisOut: [a=Tuiej9TMAAAA:8 a=CKLmnFKEmOjMGwKij9kA:9 a=UjmV-FghSN_NPa] X-AnalysisOut: [pwtb0LSvYxxjwA:4] Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 -58 fixed a repeatable crash I was seeing in fork on every machine on which I ran a particular big hairy application (http://software.jessies.org/terminator). Nothing new there, so I only spam you with my thanks because the machines in question were all running 1.5, though the executable was compiled with 1.7. I didn't notice that symptom reported previously. I'd got as far as proving that the problem didn't happen in -50 and did in -51 through -57 inclusive. I was hoping to pin the change in behavior more conclusively on Dave Korn's big memory allocation check-in of 2009-07-07, which I believe was between -50 and -51, before reporting it. This is somewhat contrary to Corinna's statement in the -58 announcement that the problem was introduced in -49. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple