X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:content-type
	:content-transfer-encoding:date:from:to:cc:subject:in-reply-to
	:references:message-id; q=dns; s=default; b=QEvfLI3ejFKzw9lRXs0c
	e9MQtdGP6geff6jfR5hhAIdCw55NC2WE5Dsa5ejRvPi062FiDOGEJYSQ16Er2yxe
	bNyRUc5CI2bonVv2wGfC3cckKcdG1472cm+dbwH/9ysEAlq3dTDhHqkmfZVt8Zfc
	1KErMfmmjvGVH0AxXZM9iOw=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:content-type
	:content-transfer-encoding:date:from:to:cc:subject:in-reply-to
	:references:message-id; s=default; bh=uLzP+25EvOC94zR+PlaKyTxZ4D
	U=; b=OHWzOMFStB3uiFO+GBf+ZMnIO46Z2DJLKfb4NXzN0m3Kx4n7/Xy9xl6p+H
	PDCfxvKph++h+rfYfEI69k3Mcfbdgrl8OYN6mnZfC4CXBIFk3+BfWouAOoIcUoVs
	MjXVmaD2unIVJ4Q48CAtNxJLEcaAcvBM515wdg4q37vc8LUOY=
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
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=-2.3 required=5.0 tests=AWL,BAYES_00,KB_WAM_FROM_NAME_SINGLEWORD,NORMAL_HTTP_TO_IP,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 spammy=hung, packaged, printenv, in-core
X-HELO:	lb3-smtp-cloud9.xs4all.net
MIME-Version:	1.0
Date:	Tue, 28 Nov 2017 15:54:11 +0100
From:	Houder <houder AT xs4all DOT nl>
To:	cygwin AT cygwin DOT com
Cc:	djndnbvg AT gmail DOT com
Subject:	Re: sort utility goes berzerk (x86_64)
In-Reply-To:	<CAJ1FpuMVeneyhKmv0d8J_EPXjfrJ09FpVt=ojMEeJPRLyKes=A@mail.gmail.com>
References:	<177e9f9fe723eadd4a8e41e5e032d56d AT smtp-cloud9 DOT xs4all DOT net> <eeee637eb6e6b01641d33930e178cbae AT xs4all DOT nl> <20171128090329 DOT GN547 AT calimero DOT vinschen DOT de> <09fc4a030cc7abb5cabf07672e683d70 AT xs4all DOT nl> <CAJ1FpuMVeneyhKmv0d8J_EPXjfrJ09FpVt=ojMEeJPRLyKes=A AT mail DOT gmail DOT com>
Message-ID:	<4301523bfc2dc2228c495aad5b4b68ec@xs4all.nl>
X-Sender:	houder AT xs4all DOT nl
User-Agent:	XS4ALL Webmail
X-CMAE-Envelope:	MS4wfBafRmXaVm0QZ9sj3/eahz+DCv+wWsuq1KGq3+PC24ZcQlQuOfO8bYaOV1F9+E5yLVhHpl/EzjJbclF4XtVSlXMwU/wF47I6n9A+CNdhWdVngOeOHeZT S/njw31vEyYusy5fW+qQNfBXebRIYCz3Qa2pUWhYxNaWM6iuZUBLzHVL0MRjdEtgX3ZLfASxOvLwW5zsKSde0D+YKNiUSB8H4Yin348bQBXWWMntWhte9cFR +r8ccpsBuoHLX7a9vB+nRw==
X-IsSubscribed:	yes

On 2017-11-28 14:37, Doug Henderson wrote:

>>> On Nov 28 08:21, Houder wrote:
>>>> 
>>>> On 2017-11-25 14:23, Houder wrote:
>>>> > Hi,
>>>> >
>>>> > Anyone seeing this as well? sort goes berzerk on my system when piped
>>>> > into
>>>> > head (or less) when it is fed with a 'specially prepared' input file.
>>>> >
>>>> >  - only happens on x86_64
>>>> >  - does not happen for 'LC_COLLATE=C sort tt | head'
>>>> >
>>>> > 'specially prepared' input file? (see bottom of post).
>>>> 
>>>> Anyone ** NOT ** seeing this?

> Q0. What is the value of PATH reported by "printenv PATH"? Just to
> verify it matches the cygcheck reported path, and to confirm that
> cygwin directories proceed windows folders.

64-@@ printenv PATH
/usr/local/bin:/usr/bin:/drv/c/WINDOWS/system32:/drv/c/WINDOWS:/drv/c/WINDOWS/System32/Wbem:/home/Henri/bin

> Q1. What is output of "which -a sort"? Is there only one sort in the 
> path?

64-@@ which -a sort
/usr/bin/sort
/drv/c/WINDOWS/system32/sort

> Q2. What is output of "sort --version"? Confirm if it is "sort (GNU
> coreutils) 8.26".

64-@@ sort --version
sort (GNU coreutils) 8.26
Packaged by Cygwin (8.26-2)
...

64-@@ /usr/bin/sort --version
sort (GNU coreutils) 8.26
Packaged by Cygwin (8.26-2)
...

> Q3. What happens when you run "sort --check FILE" on a problem file?

64-@@ sort -c tt | head
64-@@ echo $?
0

> Q4. After you kill a hung sort, are there files left over in /tmp? I
> am wondering if the problem files are too big to do an in-core sort,
> and something goes wrong when it switches to a temp file sort, but not
> for smaller or larger input files where it correctly predicts which
> type of sort it needs to do. Possibly using the "--buffer-size=N"
> option will change the behavior, making smaller input files fail and
> failing ones work.

Never noticed any file in /tmp, /usr/tmp and /var/tmp, both while sort
was still running, and after I killed it.

I will experiment with --buffer-size=N

Henri

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