This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Hyperthreading problem: remote access
- From: Brian Ford <ford at vss dot fsi dot com>
- To: Joris van der Sande <info at pulserate dot com>
- Cc: Cygwin List <cygwin at cygwin dot com>
- Date: Tue, 1 Feb 2005 16:32:13 -0600
- Subject: Re: Hyperthreading problem: remote access
- References: <41FD7F9D.9060608@pulserate.com> <6.2.0.14.0.20050130195041.05c31ec0@pop.prospeed.net> <41FFFC27.4000808@pulserate.com>
- Reply-to: cygwin at cygwin dot com
On Tue, 1 Feb 2005, Joris van der Sande wrote:
> Larry Hall wrote:
> > Chris has already answered that question earlier in
> > the discussion. He needs physical access to the
> > machine to resolve this problem. Remote access isn't
> > enough.
>
> Forgive my ignorance, but I read the archives back to
> 1 jan 2004 but found no explanation why remote access
> doesn't help the developers to track down the problem.
> Could someone please point me to the relevant postings?
>
http://sources.redhat.com/ml/cygwin/2005-01/msg00521.html
Specifically, cgf wrote:
>Fixing this problem will be difficult. Dealing with race conditions
>like this always is difficult. 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 (I just had
>to do one of these yesterday while debugging a non-thread race
>condition).
Mostly, this is a case of a volunteer not wanting to deal with that sort
of hassle. YMMV.
--
Brian Ford
Senior Realtime Software Engineer
VITAL - Visual Simulation Systems
FlightSafety International
the best safety device in any aircraft is a well-trained pilot...
--
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/