X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-2.5 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,TW_XV,T_TO_NO_BRKTS_FREEMAIL
X-Spam-Check-By:	sourceware.org
MIME-Version:	1.0
In-Reply-To:	<20110304095224.GB3480@calimero.vinschen.de>
References:	<20110302130651 DOT 17593ulkc6umco2j AT messagerie DOT si DOT c-s DOT fr> <20110302140857 DOT 8746705bfur7cwa1 AT messagerie DOT si DOT c-s DOT fr> <AANLkTi=duD4zd9wRNvOD0jER9Su7eDTu3=7S_LMHofLb AT mail DOT gmail DOT com> <20110304095224 DOT GB3480 AT calimero DOT vinschen DOT de>
Date:	Fri, 4 Mar 2011 12:42:15 +0000
Message-ID:	<AANLkTi=JH2tju0huo2kiUMkxHFiou2Jenmp5zrM9Zrzt@mail.gmail.com>
Subject:	Re: winmm.dll error 487 is easily reproducible
From:	Andy Koppe <andy DOT koppe AT gmail DOT com>
To:	cygwin AT cygwin DOT com
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT 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

On 4 March 2011 09:52, Corinna Vinschen wrote:
> On Mar =C2=A04 05:09, Andy Koppe wrote:
>> On 2 March 2011 13:08, EXCOFFIER Denis wrote:
>> > P.S.: By the way, what is the normal way to install snapshots? It is
>> > easy to replace cygwin1.dll (keeping around the working one), but in o=
rder
>> > to test the cygwin1 package in full (eg to check within stdio.h whether
>> > vsnprintf is included under __STRICT_ANSI__ or not)?
>>
>> You should usually install the cygwin-inst-*.tar.bz2 tarball
>> containing all the relevant headers and tools along with the DLL.
>>
>> There's a FAQ entry describing how to install it at
>> http://cygwin.com/faq-nochunks.html#faq.setup.snapshots.
>>
>> The snapshots page could do with a link to that. However, due to
>> Cygwin 1.7's ability to overwrite in-use files, including the Cygwin
>> DLL itself, it's no longer necessary to exclude the DLL when
>> unpacking, i.e. I find the following works for me:
>>
>> - Shut down all Cygwin processes, including background services.
>> - Open a Cygwin shell (with administrator rights if Cygwin was
>> installed as administrator).
>> - cd /
>> - tar xvf /path/to/cygwin-inst-*.tar.bz2
>
> Just for the records:
>
> At this point you just have to keep in mind that the old DLL has now
> been moved to the trash bin. =C2=A0Every new process started from here, by
> fork or by exec, would load the new DLL. =C2=A0That would very likely col=
lide
> with the memory layout of the old DLL so you're risking a crash. =C2=A0Yo=
u're
> lucky that the processes up to here don't fork during un-taring...
>
>> - Close shell.
>
> ...so that's the only sane thing to do here.

To avoid this sort of manual faffing about and increase the chances of
people testing snapshots, how about delivering them as test releases
through setup.exe, with announcement to cygwin-announce? Not every one
of them, especially early in a development cycle, but I think it would
make sense when trying to knock a release into shape.

Andy

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

- Raw text -