X-Spam-Check-By: sourceware.org
Message-ID: <45BF6042.8050508@spiresoftware.com>
Date: Tue, 30 Jan 2007 07:12:02 -0800
From: Glenn Serre <gaserre AT spiresoftware DOT com>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
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
References: <1170136590 DOT 45bede0eefb74 AT imp DOT free DOT fr> 	 <45BEE298 DOT 8090100 AT spiresoftware DOT com> <ba40711f0701300536l1537f36at32911d5af856c6a7 AT mail DOT gmail DOT com>
In-Reply-To: <ba40711f0701300536l1537f36at32911d5af856c6a7@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

Good morning,

Lev Bishop wrote:
> On 1/30/07, Glenn Serre  wrote:
>> I have no working patch, I was going to use this problem as an 
>> opportunity for
>> my first attempt to build and debug the cygwin DLL (while maybe even 
>> charging a
>> client for it) but it looked to me as if it may already be being 
>> addressed.
>> Looking again, I see that this might not be that case, so I'll see 
>> what I can do
>> (no promises, as I'm a newbie at cygwin development).
> 
> In cases like this, a generally useful thing you can do is to go try
> snapshots from
> http://cygwin.com/snapshots/
> and try to figure out between which 2 versions the problem first
> appeared. If you post the reult of this to the list, then someone can
> often fix it easily, but if you wanted to have a go yourself,  you can
> look at the changelogs for that snapshot and frequently it will be
> obvious which change was to blame.


The 2006-12-11 version of cygwin1.dll has the problem.
The 2006-12-05 version does not.

I don't see an obvious smoking gun in the changelog (I haven't even looked at 
the code yet) but there do seem to be candidates.

Thanks,
--Glenn S.



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


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