Message-ID: <20100704145638.en72z2t3y8cg800w@mail.zih.tu-dresden.de>
Date: Sun, 04 Jul 2010 14:56:38 +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>	<20100628185835.wweg4rnd01wcsgoo@mail.zih.tu-dresden.de>	<4C291317.6060909@cygwin.com>
In-Reply-To: <4C291317.6060909@cygwin.com>
MIME-Version: 1.0
Content-Type: text/plain;	charset=UTF-8;	DelSp="Yes";	format="flowed"
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
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


>> Is there a way to investigate whether a unknown BLODA-app or something e=
lse
>> causes the problem?
>
> Typically the process is just look at the security software that you have
> installed and try uninstalling one-by-one until the problem is resolved.
> Then you can reinstall all the other ones and report the problem to the
> vendor of the offending app.
>

@ Corinna & Larry: Thanks for your hints and suggestions!

I did what Larry wrote, there was only one piece of security software=20=20
to uninstall. No luck. Fresh setup of cygwin. Still no luck. Reinstall=20=
=20
new version of my av. Of course no luck...
I can add to the problem-report that not only top doesn't work in 95%=20=20
of invocations. On a random basis I get also fork()-errors or=20=20
segfaults when launching one more xterm-window.

Well, looks like I'm not hacker enough to solve it all on my own. So,=20=20
to investigate the issue: is there some super-verbose or debug-mode to=20=
=20
run cygwin/X/xterm/top to get further information what's going wrong?

Probably everybody can easily imagine, that I'm not keen on rolling=20=20
back the configured system to a plain unpatched W7 just to add one=20=20
more item to BLODA. That's where my question regarding verbose/debug=20=20
comes from.

Furthermore I see from the list, lot's of people have issues with=20=20
their cygwin/cygwinX installations on their w7 64bit boxes, often=20=20
showing somehow similar symptoms. At the people who got it running=20=20
without problems, segfaults, fork()-errors: What's the trick?=20=20
Disabling UAC and Defender? Using an English language Windows? Turning=20=
=20
on/off DEP, VT-x or whatever?


Thanks in advance, Philipp

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