DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:subject:date:message-id:mime-version
	:content-type; q=dns; s=default; b=M+jnGE0d93Rb3dCATE0xOh1LXRSe2
	zKx6TOo6w8yWYKQofWwotCcHZBx01UCAoqKMr7n+cktHYYRFfCYTvyMkwTkPp6Sx
	VAAtUzzlS0Gm6rcDsjbCyy/fHh+TzUNdBCAO1i1L16JZzDT+mPEuSh5UAq0HdyoH
	l55atXMqtt3TEo=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
From: Achim Gratz <Stromeko AT nexgo DOT de>
To: cygwin AT cygwin DOT com
Subject: top exits spuriously on R2016
Date: Fri, 01 Jun 2018 21:41:49 +0200
Message-ID: <876032xpj6.fsf@Rainer.invalid>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain


I've got my new R2016 server re-configured to only have a single
processor group instead of two (and HT switched off to match the
available memory better to my median memory usage per core).

However, top still spuriously exits (I originally thought it had to do
with top not being processor group aware).  When starting it in an RDP
session in mintty, it will most of the time exit without any output at
all or after clearing the screen.  Running it remotely via ssh through
screen / tmux it'll typically exit while in the middle the first refresh
(after the initial display) partially emitted.  Piping stdout and stderr
through less or into a file will often show the error message

top: failed openproc: Bad address

before the exit.  Running it via strace in a separate window it keeps
working just fine.  I think it may be hitting a race condition, but I'm
running out of ideas with this Heisenbug.

Is anyone seeing something similar and/ or having suggestion for a
workaround?


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Factory and User Sound Singles for Waldorf rackAttack:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds

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