Message-ID: <4E85E693.1060705@gmail.com>
Date: Fri, 30 Sep 2011 17:56:03 +0200
From: Marco Atzeri <marco.atzeri@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:6.0.2) Gecko/20110902 Thunderbird/6.0.2
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: STATUS_ACCESS_VIOLATION
References: <32557806.post@talk.nabble.com> <4E859D04.3040902@gmail.com> <32569776.post@talk.nabble.com>
In-Reply-To: <32569776.post@talk.nabble.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

On 9/30/2011 5:33 PM, Marc Girod wrote:
>
>
> marco atzeri-4 wrote:
>>
>> Problem reports:       http://cygwin.com/problems.html
>> so at least we have an idea of your system
>>
>> in addition, have you checked
>> http://cygwin.com/faq/faq.using.html#faq.using.bloda
>>
>> Antivirus and driver are the most likely culprits.
>>
> Yes, I know both pages...
> Maybe you are right and I have a *problem* which I ought the *report*.
> But that's not exactly the way I was looking at it.
>
> Marc

yeah, I understand, some time I have the same view.

My experience is that using the standard "problem report" improve the
chance to correctly identify the root cause and reduce the number of
guess that everyone could have.

You can also try a cygwin snapshots
http://cygwin.com/snapshots/

there are some recent improvements that seem real effective
in particular fork cases.

Regards
Marco


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