Message-ID: <1170136590.45bede0eefb74@imp.free.fr>
Date: Tue, 30 Jan 2007 06:56:30 +0100
From: jm DOT challier AT free DOT fr
To: cygwin AT cygwin DOT com
Subject: Re: Newly-installed bash 3.2.9-10 (cygwin 1.5.24-1) exits when I try to execute a program
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
User-Agent: Internet Messaging Program (IMP) 3.2.5
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com

Good morning.

I'm quite happy to find this thread - I thought I was the one who messed things
up... ;^)

I experience exactly the same problem : XP64, recently updated cygwin -> bash
exits with code 128 when trying to execute anything (except builtins, of
course). Same thing for gcc (tried from emacs too).

To answer a question that was asked in the "xp64 fails with latest download"
thread (which deals with the same problem) : I have only one cygwin1.dll file on
the system.

> Reverting to cygwin 1.5.23 worked.
> Is someone working to fix this, or is this an opportunity for me to submit a
patch?

If you have a patch working, pease go ahead. Reverting to 1.5.23 is not a patch,
but a workaround :-) Meanwhile, I'll stick with my good'ol'32-bit laptop...

By the way, in case it's a version consistency problem, what mirror are you
using ? I'm using ftp://mirror.cict.fr/ - nearest from home.

TIA

JMC


--
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/