X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-0.6 required=5.0 tests=AWL,BAYES_50,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: sourceware.org MIME-Version: 1.0 Date: Fri, 14 May 2010 16:28:29 -0400 Message-ID: Subject: Re: 1.7.5-1: execv fails in .exe compiled From: Stephen Morton To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=ISO-8859-1 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 On Thu, 13 May 2010 17:49:08 -0400, Larry Hall wrote: >On 5/13/2010 5:45 PM, Stephen Morton wrote: >>The problem appears to be cygwin 1.7-specific. (*) >> >> I get a stackdump as follows. I find that I get a stackdump under a >> cygwin shell (DOS terminal) but not under mintty so I'm not 100% sure >> the stackdump is for the correct error. > >Do you have a ? http://cygwin.com/acronyms/#WADR , this was in my _very_first_email_ "9. I have tried making a dummy program that's just a wrapper for the failing code and passing in all the same data as the failing case. And it works. That really confuses me." I do have a binary --an only slightly modified gcc 3.4.6 cross-compiler-- that always fails. And there is a simple testcase that fails with that binary. But I doubt that really does anybody any good. For now, my team will continue our prototyping on Win7 + Cygwin 1.5. We'll re-evaluate when cygwin 1.7 seems a bit more mature (less frequent updates with fixes to less severe-sounding problems). I know this isn't a particularly recommended configuration, but it seems to be working. Stephen -- 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