From: Andrew Schulman <schulman.andrew@epa.gov>
To: cygwin@cygwin.com
Subject: Re: lftp / zlib problems
Date: Wed, 27 Sep 2017 14:22:00 -0000 [thread overview]
Message-ID: <aqcnsc938ml6rkpvkrvmp8c42tr8f4sb8f@4ax.com> (raw)
In-Reply-To: <BN6PR2001MB10748B4DA42EE0012D4DA8E6F17A0@BN6PR2001MB1074.namprd20.prod.outlook.com>
> From: Harri T.
> > Hi all,
> >
> > After updating Cygwin 32-bit we have had problems with all the
> > combinations of lftp 4.7.7.-1 / 4.8.0-1 and zlib 1.2.8-3 / 1.2.11-1.
> > ...
> > assertion "ptr(x.heap_index)==&x" faSKiled: file
> > "/home/ASchulma/dev/cygwin/lftp/lftp-4.8.0-1.i686/src/lftp-
> > 4.8.0/src/xheap.h", line 127, function: void
> > xheap<T>::remove(xheap<T>::node&) [with T = Timer]
> >
> > generating a stackdump file.
> >
> > Is there something we can do to avoid these issues?
>
> To add some weight to Harri T.'s message, I've reported the same problem twice:
>
> https://sourceware.org/ml/cygwin/2017-08/msg00051.html
> https://sourceware.org/ml/cygwin/2017-09/msg00014.html
>
> -Ken Nellis
OK. I'm sorry for the delay in dealing with this problem. Clearly 4.8.0 is
broken in Cygwin, and the build of 4.8.1 fails so far so that's no help.
Meanwhile 4.7.8 is out so I'll try that and see if it fixes the problems
with 4.7.7 and 4.8.0.
Andrew
--
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
next prev parent reply other threads:[~2017-09-27 14:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-01 14:46 [ANNOUNCEMENT] lftp 4.8.0-1 Andrew Schulman
2017-09-25 12:55 ` lftp / zlib problems Harri T.
2017-09-25 13:53 ` Nellis, Kenneth
2017-09-27 14:22 ` Andrew Schulman [this message]
2017-09-27 16:10 ` Andrew Schulman
2017-09-27 19:10 ` Nellis, Kenneth
2017-10-04 11:05 ` Andrew Schulman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aqcnsc938ml6rkpvkrvmp8c42tr8f4sb8f@4ax.com \
--to=schulman.andrew@epa.gov \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).