From: Christopher Faylor <cgf-no-personal-reply-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: cygwin1.dll problem with Hyperthreaded machines (reprise)
Date: Fri, 30 Jul 2004 18:10:00 -0000 [thread overview]
Message-ID: <20040730161203.GE27432@trixie.casa.cgf.cx> (raw)
In-Reply-To: <OFBE0EB9A0.9D781CB8-ON85256EE1.00579FBD-85256EE1.00583091@abinitio.com>
On Fri, Jul 30, 2004 at 12:03:16PM -0400, Chuck McDevitt wrote:
>On Fri, Jul 30, 2004 at 11:41:39AM -0400, Chuck McDevitt wrote:
>>I've also been trying to convince my company to donate a hyperthreaded
>>machine to someone on the cygwin project, but so far, management's
>>reaction is "How do we know anyone will work on the problem, even if we
>>give them a machine?" And I'm not even sure who we would send the
>>machine to.
>
>cgf wrote:
>>I would probably be the best candidate and I would work on it if a
>>machine was donated.
>>
>>FWIW, I have a multi-cpu machine and have, in the past, run the
>>supposedly failing tests for days without problem.
>>
>>Btw, please don't include raw email addresses in your replies.
>
>The problem only appears if there is something else running
>on the box that is creating processes, such as a large make,
>or some other kind of heavy load.
>
>I've run the test for a good day or so on a box with no other load, and
>the problem didn't occur, but doing several makes and/or builds in
>Visual Studio at the same time, and the bug would occur very quickly.
>
>P.s. I've tried to get this stupid Lotus notes to not send any raw
>email addresses, but it's hard to tell what it is really sending, as it
>doesn't show me what the e-mail will
>look like to you. Notes is a major pain-in-the-ass, but it's what I'm
>stuck with here.
(Well, whatever you're using, you're making it pretty hard to have a
normal mailing list discussion since you're top-posting and not using
any attribution.)
Anyway, I have tried doing other things while the tests were running
without problems. My SMP system is a dual PIII 733, so maybe it just
isn't powerful enough to trigger the problem.
--
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/
next prev parent reply other threads:[~2004-07-30 16:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-30 14:06 Cygwin1.dll " Volker Bandke
2004-07-30 14:49 ` cygwin1.dll " Christopher Faylor
2004-07-30 16:03 ` Cygwin1.dll " Chuck McDevitt
2004-07-30 16:17 ` cygwin1.dll " Christopher Faylor
2004-07-30 17:09 ` Chuck McDevitt
2004-07-30 18:10 ` Christopher Faylor [this message]
2004-07-30 18:31 ` Volker Bandke
2004-07-30 18:42 ` Larry Hall
2004-07-30 19:24 ` Volker Bandke
2004-07-30 20:19 ` Larry Hall
2004-07-30 21:30 ` Volker Bandke
2004-07-30 21:32 ` Larry Hall
2004-08-02 15:07 ` Larry Hall
2004-08-02 16:29 ` Christopher Faylor
2004-08-05 9:28 Errol Smith
2004-08-05 11:30 ` Christopher Faylor
2004-08-05 12:21 ` Dave Korn
[not found] <1091705732.26208.ezmlm@cygwin.com>
2004-08-06 2:17 ` Errol Smith
2004-08-07 12:05 ` Gary R. Van Sickle
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040730161203.GE27432@trixie.casa.cgf.cx \
--to=cgf-no-personal-reply-please@cygwin.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).