This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: child_copy: linked dll data write copy failed
- From: cwcarlson <cwcarlson at cox dot net>
- To: cygwin at cygwin dot com
- Date: Sat, 22 Dec 2007 10:41:44 -0800 (PST)
- Subject: Re: child_copy: linked dll data write copy failed
- References: <000501c61bce$e52bbe60$025ca8c0@starwhite.net> <000001c61beb$8b1806f0$025ca8c0@starwhite.net>
I'd like to know how you determined that a DLL was loaded with every process.
I'm having the same problem, but I don't know how to debug it.
I had some time to debug this, and found that it was the "Logitech Process
Monitor" service, which I had recently installed (and forgotten about). It
apparently causes a DLL to be loaded into every process, which was causing
the problem. Once I set the service to Manual start, Cygwin-X started
perfectly.
I'm good to go for now, if someone has any insights to help figure out why
this is happening, or wants to look into it further, I'm still interested.
--
View this message in context: http://www.nabble.com/child_copy%3A-linked-dll-data-write-copy-failed-tp2438176p14472041.html
Sent from the Cygwin list mailing list archive at Nabble.com.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/