Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
Message-Id:	<4.3.1.2.20010416112827.0200d460@pop.ma.ultranet.com>
X-Sender:	lhall AT pop DOT ma DOT ultranet DOT com
X-Mailer:	QUALCOMM Windows Eudora Version 4.3.1
Date:	Mon, 16 Apr 2001 11:33:25 -0400
To:	Troy Noble <troy DOT noble AT channelpoint DOT com>,
	"'cygwin AT cygwin DOT com'" <cygwin AT cygwin DOT com>
From:	"Larry Hall (RFK Partners, Inc)" <lhall AT rfk DOT com>
Subject:	Re: What's a good stable snapshot DLL?
In-Reply-To:	<8F23E55D511AD5119A6800D0B76FDDE11E0F06@cpex3.channelpoint.
	com>
Mime-Version:	1.0

At 10:45 AM 4/16/2001, Troy Noble wrote:
>Am having some relatively frequent Dr. Watson dialogs on Win2K and NT 4
>SP6a.
>Access Violations.  Using 1.1.8-2 version of the DLL from a "cygwin/latest"
>mirror.
>
>It's seems to happen in all sorts of places... echo.exe, make.exe, bash.exe,
>basepath.exe.  Seems to be somewhat random, in other words I can't reproduce
>it the same way twice.  And it only seems to occur on machines where I have
>cygwin on the d: drive instead of the c: drive.
>
>So am willing to try a snapshot of the DLL as is frequently suggested on the
>list.
>My question is, what is a good stable version I can try (looking for minimal
>risk if
>possible).  Saw one reference to
>
>ftp://mirrors.rcn.net/mirrors/sources.redhat.com/cygwin/snapshots/cygwin1-20
>010411.dll.bz2
>
>but that seems awfully recent.  Is it generally safe using ones that recent
>given
>that these are built off of developer sources almost daily?


Snapshots are not generally considered stable.   They are works in progress.
If submissions build, a new snapshot is created.  If not, there's no 
snapshot.  Whether they "work" or not is determined by those that run them.
If you intend to try/use a snapshot, you should:

   1. Backup any previous DLL/environment you have that you may want to fall
      back to.

   2. Be willing to try a few to see if they help solve your problems without
      creating others.

   3. Report the results of (2).

   4. Preferably be willing to help debug issues you find.


Larry Hall                              lhall AT rfk DOT com
RFK Partners, Inc.                      http://www.rfk.com
118 Washington Street                   (508) 893-9779 - RFK Office
Holliston, MA 01746                     (508) 893-9889 - FAX


--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

- Raw text -