Mail Archives: cygwin/2011/12/22/09:48:10
On 23/12/11 01:33, Corinna Vinschen wrote:
> On Dec 23 00:07, Shaddy Baddah wrote:
>> On 22/12/11 22:19, Corinna Vinschen wrote:
>>> On Dec 22 22:11, Shaddy Baddah wrote:
>>>> 69 126706 [main] sh 3824 build_env: envp 0x61266AB4, envc 47
>>>> 37 126743 [main] sh 3824 child_info::child_info: subproc_ready 0x234
>>>> 589 127332 [main] sh 3824 seterrno_from_win_error:
>>>> /netrel/src/cygwin-snapshot-20111219-1/winsup/cygwin/spawn.cc:692
>>>> windows error 5
>>>> 59 127391 [main] sh 3824 geterrno_from_win_error: windows error 5 ==
>>>> errno 13
>>>> 74 127465 [main] sh 3824 child_info_spawn::worker: CreateProcess
>>>> failed, Win32 error 5
>>>> 196 127661 [main] sh 3824 stat64: entering
>>>
>>> Well, CreateProcess fails with "access denied". There must be a reason
>>> for that, but I don't know what it is and I don't know what to look for.
>>> Try bisecting the snapshots.
>>>
>> * spawn.cc (child_info_spawn::worker): Add CREATE_BREAKAWAY_FROM_JOB
>> to all spawned processes. Explain why.
>>
>> Looks rather innocuous, so don't understand why it is causing me
>> problems.
>
> Indeed. I just tried again on another W7 64 bit machine and it still
> works for me. I'm wondering if the culprit is a virus scanner or
> something similar running on your system. Can you please check that?
Indeed we do run a virus scanner, McAfee VirusScan
Enterprise. However I can't turn it off by policy. In fact, we run a
desktop environment where there are a small number of actions limited
by policy. But nothing I have encountered so far that is overly
restrictive.
The virus scanner has an extensive access log. It doesn't list
anything with regards to my Cygwin activities that might account for
the problem. But you never know. I might ask our desktop admin
tomorrow if they'll allow me to disable the scanner briefly to test.
>
>
> Other than that I might have a solution. I applied a patch which only
> adds the CREATE_BREAKAWAY_FROM_JOB flag if the calling process is member
> of a job and the job allows a breakaway. It works in my limited
> testing, but it would be important to know if it works for you, too, of
> course. If you're not set up to build your own Cygwin DLL, please test
> the next developer snapshot.
Yes, unfortunately I am not set up at the moment to build dlls, so
I'll eagerly await the next snapshot.
Thanks for all your help in getting this far.
Regards,
Shaddy
--
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
- Raw text -