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:date:message-id:from:to:subject:references :in-reply-to:content-type; q=dns; s=default; b=VLVaOWTVBUJO+sC2q wu5+WhNYlYX7uwvuf4Gm+K5WoWWD4Yc4Zx6zQd4G6LuEjP/1GStmyA1U3uzsJnD9 dJjmrKBs02q4w2ZfeJqQ5LFCYWYuO+cQkFMCpXTrPrcaHdH+tkc1DmHbAGFfn+CZ +/MvKRrf6KjgVL5LSS5T+YHdHQ= 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:date:message-id:from:to:subject:references :in-reply-to:content-type; s=default; bh=fbO1Ku08u/LFXbYRsKmsuFz oaUQ=; b=ei4xs+vf/lcD5kz8rRFF+ASikNVEMAmKscte+uvZXWf1D8tWfNxO9Yq 2aHREtAS/fUMwN9jEcJH3VOnJQfD5z8WqP91T+jzEhM6fkmfPOeVKZYLnY8XZDQM w7ct9HmMxVIUF6y6DCGUNuVK0Xk9m2FiTel3/YwpewOZiGUoBqTg= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , 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,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 spammy=achim, Achim, $TMPDIR, Firefox X-HELO: lb3-smtp-cloud9.xs4all.net Date: Thu, 30 Nov 2017 01:44:00 +0100 Message-ID: <2fe67fc4abf59f71c1d84a3264b5344a@smtp-cloud9.xs4all.net> From: Houder To: cygwin AT cygwin DOT com Subject: Re: sort utility goes berzerk (x86_64) References: <177e9f9fe723eadd4a8e41e5e032d56d AT smtp-cloud9 DOT xs4all DOT net> <20171128090329 DOT GN547 AT calimero DOT vinschen DOT de> <09fc4a030cc7abb5cabf07672e683d70 AT xs4all DOT nl> <944c377d08d67cda987edfcf4389ee89 AT xs4all DOT nl> In-Reply-to: Content-Type: text/plain; charset=UTF-8; format=fixed User-Agent: mua.awk 0.99 X-CMAE-Envelope: MS4wfLBXR3rSjcMGk1sGlEtqo9j8q2+MKHhcST4B7w+I4SAwwpCIgIL+kviHztZ4fN0jvqqu7EWgKUM3CR87/xrrBjW3iQCVhK8oUWImZ3IoZU67UDCvAxXm +lJPgrkdca0glZIBK/nK77uGeOdEpqhQvVE045zPtxm8idLowAniQWgPQb1Pl43ZL4h3dlQF8AtuDA== On Wed, 29 Nov 2017 15:39:45, Brian Inglis 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? Brian and Achim, thanks for the interest in this peculiar problems. Currently my Windows 7 is not much of a tool to me. I have ripped out about everything in an attempt to find the cause of the weird behaviour of sort. Ripped out everything? Visual Studio (and anything related to it), Firefox, F-Secure (virusscanner), etc., etc., etc. ... However, sort still behaves in the same weird manner. That is, NOT if invoked as follows (in a script): #!/bin/bash trap "" PIPE # make sort ignore the SIGPIPE signal export LC_COLLATE=en_US.UTF-8 exec /usr/bin/sort ${1+"$@"} 2> /dev/null .. meaning if SIGPIPE is ignored by sort (which would kill it otherwise), it will notice the broken pipe while writing, and terminate itself. What also amazes me, is the stack dump of the 'sort thread', which I got using the Process Explorer by Mark R. ntoskrnl.exe!memset+0x61a ntoskrnl.exe!KeWaitForMultipleObjects+0xd52 ntoskrnl.exe!KeWaitForSingleObject+0x19f ntoskrnl.exe!PoStartNextPowerIrp+0xbd0 <==== ????? ntoskrnl.exe!PoStartNextPowerIrp+0x186d <==== ????? cygwin1.dll!reent_data+0x5f0 cygwin1.dll!acl_get_perm+0x9aa1 cygwin1.dll!_getreent+0x1097 sort.exe+0x5319 sort.exe+0x103e0 cygwin1.dll!cygwin_dll_init+0x11c2 cygwin1.dll!setprogname+0x35c3 cygwin1.dll!setprogname+0x3674 This is the stack dump of sort when it occupies the core completely, and has become unresponsive. I do not know anything about the internals of Windows, but it amazes me to see 'a power related function call' on the stack of sort. > Have you checked for permissions problems on $TMPDIR if set, or /tmp? Yes, all these things have been checked by me ... Henri (message sent from Fedora, as I cannot currently use Windows 7) ===== -- 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