Message-ID: <20100628185835.wweg4rnd01wcsgoo@mail.zih.tu-dresden.de>
Date: Mon, 28 Jun 2010 18:58:35 +0200
From: "P. Goldmann" <s5683798@mail.zih.tu-dresden.de>
To: cygwin@cygwin.com
Subject: Re: problems running "top" task monitor
References: <20100628101527.4f72zsz5kwg8owww@mail.zih.tu-dresden.de>	<20100628113203.GC6310@calimero.vinschen.de>
In-Reply-To: <20100628113203.GC6310@calimero.vinschen.de>
MIME-Version: 1.0
Content-Type: text/plain;	charset=UTF-8;	DelSp="Yes";	format="flowed"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
User-Agent: Internet Messaging Program (IMP) H3 (4.1.3)
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Note-from-DJ: This may be spam


>> Hi!
>>
>> using cygwin 1.7.5(0.225/5/3) on a win7 x64 box I'm experiencing
>> problems running the task monitor "top":
>> The only output calling "top" produces - after one minute - is the   
>> following:
>> ==
>> login@machine ~
>> $ top
>> Aborted
>>
>> login@machine ~
>> $
>> ==
>
> Works fine for me.  The effect is rather strange.  I'd suspect a BLODA
> issue: http://cygwin.com/acronyms/#BLODA
>
>
> Corinna
>


I checked against the BLODA at
http://cygwin.com/faq/faq.using.html#faq.using.bloda

Windows Defender is not used, my AntiVirus is not on the list and does  
not seem to have
an impact.

In the mean time I was able to start "top" twice, out of some dozen  
shots. So the issue
seems to be somehow random with a 95% capability of failure.

After a failed start of "top" I also get segfaults when opening a new  
"xterm" window.

Is there a way to investigate whether a unknown BLODA-app or something  
else causes the
problem?


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