Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
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
From: "Dave Korn" <dave DOT korn AT artimi DOT com>
To: <cygwin AT cygwin DOT com>
Subject: RE: bash / snapshot combi crash
Date: Tue, 8 Mar 2005 13:35:34 -0000
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
In-Reply-To: <79F81D5F4790D344B05F489CE2AC8AB71470B0@dubexdc03.dubex.net>
Message-ID: <SERRANOOYr3DHz5pwPP00000010@SERRANO.CAM.ARTIMI.COM>
X-OriginalArrivalTime: 08 Mar 2005 13:35:34.0216 (UTC) FILETIME=[B476CC80:01C523E3]

----Original Message----
>From: David Dindorp
>Sent: 08 March 2005 05:00


> Stack trace:
>  Exception: STATUS_ACCESS_VIOLATION at eip=[SNIP]
>  End of stack trace (more stack frames may be present)

> I'd be happy to make a test case, but I'm quite busy doing other
> test cases and real work at the moment.  If this report is not
> helping anyone at all, let me know.


  The stackdump is no help unless you decode it yourself: see
http://www.cygwin.com/ml/cygwin/2005-03/msg00154.html for why.




    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....


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