Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Wed, 02 Feb 2005 20:05:46 +0100 From: Joris van der Sande Subject: Re: Hyperthreading problem: remote access In-reply-to: <20050201223806.GB8400@trixie.casa.cgf.cx> To: cygwin AT cygwin DOT com Message-id: <4201248A.5050901@pulserate.com> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) References: <41FD7F9D DOT 9060608 AT pulserate DOT com> <6 DOT 2 DOT 0 DOT 14 DOT 0 DOT 20050130195041 DOT 05c31ec0 AT pop DOT prospeed DOT net> <41FFFC27 DOT 4000808 AT pulserate DOT com> <20050201223806 DOT GB8400 AT trixie DOT casa DOT cgf DOT cx> Christopher Faylor wrote: > However, here is one of the times I repeated that I > don't want to do this over the internet: > [...] > Fixing this problem will be difficult. Dealing with > race conditions like this always is difficult. Indeed, as an embedded software designer I know this first hand. > I don't want to do this over the internet. It would > be too painful and there is no guarantee that I > could even do it at all. It could involve machine > reboots Fair enough. It is already amazing how much effort you and other volunteers put into cygwin. Obviously it is your own choice whether you want to put up with the hassle of remote debugging and possibly many re-logins. > I can't imagine why this would be a useful thing to > discuss here. I just assumed there was a technical reason why remote debugging would not work, that I had overlooked. The offer still stands in case another developer likes to give it a try. /Joris -- 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/