X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-1.6 required=5.0	tests=AWL,BAYES_00,SPF_HELO_PASS,T_RP_MATCHES_RCVD
X-Spam-Check-By: sourceware.org
To: cygwin AT cygwin DOT com
From: Andrew Schulman <schulman DOT andrew AT epamail DOT epa DOT gov>
Subject: Re: Request: LFTP Update to 4.2.2
Date: Wed, 27 Apr 2011 10:20:04 -0400
Lines: 19
Message-ID: <8c9gr65884e3a890aeemea0f9kvdmhnhs3@4ax.com>
References: <BANLkTi=2LwA4iZDu05Jev2He+ouPpX=1_g AT mail DOT gmail DOT com>	<r6gdr6l2ldmttp22r9tnvu5hkp7kdh8j7g AT 4ax DOT com>	<BANLkTimQfoKXZSbiytg1V+wVdcy9aj4Z7A AT mail DOT gmail DOT com>	<40ldr61io1ml20gv97g6r65lipubqc1mla AT 4ax DOT com>	<BANLkTi=V4wgePBBATpUqFPVx8T896Bzxow AT mail DOT gmail DOT com> <BANLkTi=2eMWUyniBXP1g3UCHN41h-MAEiQ AT mail DOT gmail DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Archive: encrypt
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

> On 26 April 2011 21:52, Chris Sutcliffe wrote:
> > Seems like this build is broken, no matter what I try with it, I get
> > the results similar to the following:
> >
> >    493 [main] lftp 4024 exception::handle: Exception: STATUS_ACCESS_VIOLATION
> >   1453 [main] lftp 4024 open_stackdumpfile: Dumping stack trace to
> > lftp.exe.stackdump
> 
> <snip>
> 
> It works OK on my WinXP laptop at work (32-bit), I see these errors on
> my Win7 laptop (64-bit) at home.  Guess I'll have to do some digging.

OK, thanks.

I build my packages on a WinXP-32 machine, and test them there.  I've never
done any testing on 64-bit.  I do have a Win7-64 machine at home, and
Cygwin runs fine there - I can do some testing there to see if I get the
same results as you.


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