* Re: "Hyperthreading" problems
[not found] <41D1D2B2.4030200@exalead.com>
@ 2004-12-28 22:29 ` Stephane Donze
2004-12-28 23:15 ` Christopher Faylor
` (2 more replies)
0 siblings, 3 replies; 12+ messages in thread
From: Stephane Donze @ 2004-12-28 22:29 UTC (permalink / raw)
To: cygwin
Hi,
Thank you for your reply. You are right, I did not look at the code, and
I certainly do not pretend to be able to fix this problem.
I am sorry to have to say that, but your message is a very good example
of the fundamental difference between a project that is useable and
reliable, and a project that "almost works" and will never do more that
that.
The problem I reported is known for almost 2 years (posted by Henrik
Wist, 20 Mar 2003, subject was "cygwin commands sometime hang on
dual-processor (WinNT-SP5)"). I don't care if it is the same bug or not,
the fact is that cygwin has a critical problem (i.e. something that
prevent users to use even simple commands like 'ls' !!) on
multiprocessor machines and nobody seems to care about it. You cannot
just expect people to "wait until you someday have a system that shows
the problem" everytime they encounter a bug.
If you guys want cygwin to be used by real people, in real life
production or development environments, you should go a bit further than
"I don't have the problem on my computer, so fix it yourself". If you
don't want to or are not able to pay attention to "real world" bugs,
cygwin will probably never be more than an "almost working" program
that runs on your computer the time to take nice screenshots, but fails
miserably when users try to make it work in the real life.
Regards,
Stephane
NB: this post is not at all about "commercial software versus OSS",
there are lots of "industrial quality" open source projects like Apache,
MySQL, etc.
Christopher Faylor wrote:
> On Fri, Dec 24, 2004 at 09:01:17AM +0100, St?phane Donz? wrote:
>
>> we have encountered random hangs and crashes in cygwin (see output of
>> cygcheck attached to this message) on a dual-processor server running
>> Windows Server 2003. IMHO, the so-called "hyperthreading problems"
>> reported
>> recently on this mailing list just have nothing to do with
>> hyperthreading,
>> but are more generally related to multi-processor issues.
>
>
> If you have followed the thread, then you know that I have a
> multi-processor
> system and I don't have the problem.
>
>>
>
> There is no point in reposting scripts. There is no point in
> recapitulating the problem. There is no point in making obvious
> observations about what one would suspect the cause would be without
> bothering to look at the code.
>
> Your options are to fix the problem yourself or wait until I someday
> have a system which demonstrates the problem.
>
> cgf
>
>
--
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/
^ permalink raw reply [flat|nested] 12+ messages in thread* Re: "Hyperthreading" problems
2004-12-28 22:29 ` "Hyperthreading" problems Stephane Donze
@ 2004-12-28 23:15 ` Christopher Faylor
2004-12-29 0:50 ` Brian Bruns
2004-12-29 1:26 ` Brian Dessent
2 siblings, 0 replies; 12+ messages in thread
From: Christopher Faylor @ 2004-12-28 23:15 UTC (permalink / raw)
To: cygwin
On Tue, Dec 28, 2004 at 11:31:00PM +0100, Stephane Donze wrote:
>I am sorry to have to say that, but your message is a very good example
>of the fundamental difference between a project that is useable and
>reliable, and a project that "almost works" and will never do more that
>that.
>
>[snip]
>
>If you guys want cygwin to be used by real people, in real life
>production or development environments, you should go a bit further than
>"I don't have the problem on my computer, so fix it yourself". If you
>don't want to or are not able to pay attention to "real world" bugs,
>cygwin will probably never be more than an "almost working" program
>that runs on your computer the time to take nice screenshots, but fails
>miserably when users try to make it work in the real life.
You know, if you'd just waited *a week*, you probably could have laid
claim to being the first posting of this type in 2005 rather than
(hopefully) the last of 2004. I think that being first is usually much
more auspicious.
So close...
--
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/
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: "Hyperthreading" problems
2004-12-28 22:29 ` "Hyperthreading" problems Stephane Donze
2004-12-28 23:15 ` Christopher Faylor
@ 2004-12-29 0:50 ` Brian Bruns
2005-01-01 21:07 ` Stephane Donze
2004-12-29 1:26 ` Brian Dessent
2 siblings, 1 reply; 12+ messages in thread
From: Brian Bruns @ 2004-12-29 0:50 UTC (permalink / raw)
To: Stephane Donze, cygwin
On Tuesday, December 28, 2004 5:31 PM [EST], Stephane Donze wrote:
> Hi,
>
> Thank you for your reply. You are right, I did not look at the
> code, and I certainly do not pretend to be able to fix this problem.
>
> I am sorry to have to say that, but your message is a very good
> example of the fundamental difference between a project that is
> useable and reliable, and a project that "almost works" and will
> never do more that that.
Funny, Cygwin is usable and reliable here for the stuff I use it for.
Yeah, its got bugs, but every program in existance has bugs.
> The problem I reported is known for almost 2 years (posted by Henrik
> Wist, 20 Mar 2003, subject was "cygwin commands sometime hang on
> dual-processor (WinNT-SP5)"). I don't care if it is the same bug or
> not, the fact is that cygwin has a critical problem (i.e. something
> that prevent users to use even simple commands like 'ls' !!) on
> multiprocessor machines and nobody seems to care about it. You
> cannot just expect people to "wait until you someday have a system
> that shows the problem" everytime they encounter a bug.
>
Frankly, unless the developers can reproduce these bugs, they won't
get fixed. Its the stuck up attitudes of users like yourself that
make trying to fix bugs all the harder.
> If you guys want cygwin to be used by real people, in real life
> production or development environments, you should go a bit further
> than "I don't have the problem on my computer, so fix it yourself".
> If you don't want to or are not able to pay attention to "real
> world" bugs, cygwin will probably never be more than an "almost
> working" program that runs on your computer the time to take nice
> screenshots, but fails miserably when users try to make it work in
> the real life.
>
<rant>
I think you really really really need to reevaluate what you say
before you hit send.
The open source/free software developers that I communicate with/work
with wrote the stuff they did because they needed an
application/library/script for a specific need, and decided to release
the software to the public in the hope that someone else might find it
useful, and the hope that other people might contribute back.
I feel the same way myself, and anytime someone tells me that what I
work on is crap or sucks and they will never use it because it sucks,
I tell them this:
You got the program from me for free. You are not my customer. You
do not have a support contract with me. As such, I work on the
projects when I can, and at the rate which I can afford. If you have
a specific request, you can either fix it yourself, or you can
compensate me for the time I spend making the changes you want if I
don't have the ability to spare some free time.
When people want me to port an app to say, MacOS or similar, I tell
them similar things: I can't afford a Mac right now. Provide me with
a system that I can use to make it work, and I'll do my best to make
it work.
What you consider 'real people' is obviously not the same type of
people I consider 'real people'. I consider these 'real people' to be
the individuals who are on this list, who work on the project, and who
actively contribute to the project. You may use Cygwin, but until you
start actively contributing to it, and helping the developers fix the
bugs and such, you have no right to complain.
I may not be an active contributor to Cygwin, but I do work alot with
other OSS projects, and they get this same type of response from
people too, and frankly, I'm sick of it.
</rant>
>
> NB: this post is not at all about "commercial software versus OSS",
> there are lots of "industrial quality" open source projects like
> Apache, MySQL, etc.
>
Yes, and those do well because people contribute to them to make them
better.
*hint hint*
--
Brian Bruns
The Summit Open Source Development Group
http://www.sosdg.org / http://www.ahbl.org
--
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/
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: "Hyperthreading" problems
2004-12-29 0:50 ` Brian Bruns
@ 2005-01-01 21:07 ` Stephane Donze
2005-01-02 19:19 ` Larry Hall
0 siblings, 1 reply; 12+ messages in thread
From: Stephane Donze @ 2005-01-01 21:07 UTC (permalink / raw)
To: Brian Bruns; +Cc: cygwin
Brian Bruns wrote:
>>If you guys want cygwin to be used by real people, in real life
>>production or development environments, you should go a bit further
>>than "I don't have the problem on my computer, so fix it yourself".
>>If you don't want to or are not able to pay attention to "real
>>world" bugs, cygwin will probably never be more than an "almost
>>working" program that runs on your computer the time to take nice
>>screenshots, but fails miserably when users try to make it work in
>>the real life.
>>
>>
>>
>
><rant>
>I think you really really really need to reevaluate what you say
>before you hit send.
>
>The open source/free software developers that I communicate with/work
>with wrote the stuff they did because they needed an
>application/library/script for a specific need, and decided to release
>the software to the public in the hope that someone else might find it
>useful, and the hope that other people might contribute back.
>
>
That's exactly my point: what I was trying to say is that Cygwin wants
and deserves to be more than a project developped for a specific need
and released to the public "as is". An to be more than that, it needs to
have an active "technical support", that cannot expect users to fix bugs
by themselves.
>I feel the same way myself, and anytime someone tells me that what I
>work on is crap or sucks and they will never use it because it sucks,
>
>
I never, *never* said that Cygwin was crap. Cygwin is a really ambitious
project that provides a generic solution to all portablity problems
between Windows and *nix. And the fact that Cygwin is a wonderful tool
is the very reason why lots of people complain about the bugs: it is so
frustrating to have a "perfect" solution to a problem and to be unable
to use it because of a spurious, non deterministic bug.
I'm not at all opposed to help fixing this bug, and I'm already working
at gathering more information for a more complete bug report. I've had
my own load of 'mysterious' bugs and nights of bug hunting, so I
understand how hard and frustrating it can be to fix such a problem.
>I tell them this:
>
>You got the program from me for free. You are not my customer. You
>do not have a support contract with me. As such, I work on the
>projects when I can, and at the rate which I can afford. If you have
>a specific request, you can either fix it yourself, or you can
>compensate me for the time I spend making the changes you want if I
>don't have the ability to spare some free time.
>
>
In fact, Cygwin *does* sell licenses:
http://www.redhat.com/software/cygwin/ .
>
>What you consider 'real people' is obviously not the same type of
>people I consider 'real people'. I consider these 'real people' to be
>the individuals who are on this list, who work on the project, and who
>actively contribute to the project. You may use Cygwin, but until you
>start actively contributing to it, and helping the developers fix the
>bugs and such, you have no right to complain.
>
>I may not be an active contributor to Cygwin, but I do work alot with
>other OSS projects, and they get this same type of response from
>people too, and frankly, I'm sick of it.
>
></rant>
>
>
--
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/
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: "Hyperthreading" problems
2005-01-01 21:07 ` Stephane Donze
@ 2005-01-02 19:19 ` Larry Hall
0 siblings, 0 replies; 12+ messages in thread
From: Larry Hall @ 2005-01-02 19:19 UTC (permalink / raw)
To: Stephane Donze, Brian Bruns; +Cc: cygwin
At 04:08 PM 1/1/2005, you wrote:
>Brian Bruns wrote:
>>
>><rant>
>>I think you really really really need to reevaluate what you say
>>before you hit send.
>>
>>The open source/free software developers that I communicate with/work
>>with wrote the stuff they did because they needed an
>>application/library/script for a specific need, and decided to release
>>the software to the public in the hope that someone else might find it
>>useful, and the hope that other people might contribute back.
>>
>
>That's exactly my point: what I was trying to say is that Cygwin wants and deserves to be more than a project developped for a specific need and released to the public "as is". An to be more than that, it needs to have an active "technical support", that cannot expect users to fix bugs by themselves.
>
>
<snip>
>In fact, Cygwin *does* sell licenses: http://www.redhat.com/software/cygwin/ .
Ah good. So you have seen that there is already at least one response to
your assertion above. Obviously, if one expects to be able to demand action
on a particular issue, one has to have "bought" such a right. The link you
provide above is one method of buying the right to demand. I expect there
are others folks on this list that would entertain the notion of fixing
problems for compensation too, so that's another option for anyone
interested. I don't think anyone here would argue that there isn't some need
for such fee-based support avenues. And you can see by the link you provide
that Red Hat is one such avenue. The thing to remember is that this list is
not a fee-based services, which has it's benefits and it's detriments. One
detriment is there's really no leverage that a user has to demand support.
But one can ask. ;-)
--
Larry Hall http://www.rfk.com
RFK Partners, Inc. (508) 893-9779 - RFK Office
838 Washington Street (508) 893-9889 - FAX
Holliston, MA 01746
--
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/
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: "Hyperthreading" problems
2004-12-28 22:29 ` "Hyperthreading" problems Stephane Donze
2004-12-28 23:15 ` Christopher Faylor
2004-12-29 0:50 ` Brian Bruns
@ 2004-12-29 1:26 ` Brian Dessent
2004-12-29 1:51 ` Christopher Faylor
2 siblings, 1 reply; 12+ messages in thread
From: Brian Dessent @ 2004-12-29 1:26 UTC (permalink / raw)
To: cygwin
Stephane Donze wrote:
> If you guys want cygwin to be used by real people, in real life
> production or development environments, you should go a bit further than
> "I don't have the problem on my computer, so fix it yourself". If you
> don't want to or are not able to pay attention to "real world" bugs,
> cygwin will probably never be more than an "almost working" program
> that runs on your computer the time to take nice screenshots, but fails
> miserably when users try to make it work in the real life.
The real problem here is as follows: Chris and the other core developers
cannot reproduce the bug on their systems. The people reporting the bug
can neither create a simple test case that demonstrates it, nor debug
the Cygwin internals and point to a specific defect. So until one side
of this equation changes nothing is going to get fixed, no matter how
hard people beg, whine, and plead. It's not about being uncaring or
whatever, it's just the way software development works. You can't even
start to try to fix something that you cannot see or reproduce and have
nothing to work with.
Brian
--
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/
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: "Hyperthreading" problems
2004-12-29 1:26 ` Brian Dessent
@ 2004-12-29 1:51 ` Christopher Faylor
2004-12-29 15:33 ` Volker Bandke
0 siblings, 1 reply; 12+ messages in thread
From: Christopher Faylor @ 2004-12-29 1:51 UTC (permalink / raw)
To: cygwin
On Tue, Dec 28, 2004 at 05:29:10PM -0800, Brian Dessent wrote:
>Stephane Donze wrote:
>>If you guys want cygwin to be used by real people, in real life
>>production or development environments, you should go a bit further
>>than "I don't have the problem on my computer, so fix it yourself". If
>>you don't want to or are not able to pay attention to "real world"
>>bugs, cygwin will probably never be more than an "almost working"
>>program that runs on your computer the time to take nice screenshots,
>>but fails miserably when users try to make it work in the real life.
>
>The real problem here is as follows: Chris and the other core
>developers cannot reproduce the bug on their systems. The people
>reporting the bug can neither create a simple test case that
>demonstrates it, nor debug the Cygwin internals and point to a specific
>defect. So until one side of this equation changes nothing is going to
>get fixed, no matter how hard people beg, whine, and plead. It's not
>about being uncaring or whatever, it's just the way software
>development works. You can't even start to try to fix something that
>you cannot see or reproduce and have nothing to work with.
I think the thing that is perhaps missing from the equation here, is
that I have tried to take stabs in the dark and fix it a few times but
I've never been successful. I've also laid awake at nights thinking
about the problem. I've studied code at various random times in the
hopes that something would jump out at me. So far, no luck.
It's interesting that the developer has to "go a little further" to fix
this bug while nearly everyone who reports the problem (with at least
one notable exception) is content to just regurgitate the same
complaints and wait. It doesn't seem like this technique is working
very well but people keep trying it.
cgf
--
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/
^ permalink raw reply [flat|nested] 12+ messages in thread
* RE: "Hyperthreading" problems
2004-12-29 1:51 ` Christopher Faylor
@ 2004-12-29 15:33 ` Volker Bandke
0 siblings, 0 replies; 12+ messages in thread
From: Volker Bandke @ 2004-12-29 15:33 UTC (permalink / raw)
To: cygwin
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Sitting in Germany makes it difficult for me to physically send you a machine.
What I can do, though, is to virtually hand over the machine to you via the net. I have an ADSL connection with 3 megabits/sec download and 512 kilobit/sec download. I can easily attach a 100 GB drive for your use, and leave the machine to you for some time. I'll give you an administrator user id on the machine. This is the machine on which I can unfailingly reproduce the error/problem/whatever situation
With kind Regards |\ _,,,---,,_
ZZZzz /,`.-'`' -. ;-;;,
Volker Bandke |,4- ) )-,_. ,\ ( `'-'
(BSP GmbH) '---''(_/--' `-'\_)
Machine-independent: Does not run on any existing machine.
(Another Wisdom from my fortune cookie jar)
-----BEGIN PGP SIGNATURE-----
Version: PGP Personal Security 7.0.3
iQA/AwUBQdLOKR5trGyhAF0wEQL5/ACfWZNo9AZvV32zW/IUezrxuPs2VFIAn0LC
830Cp2XKkZQNFZ2m39PoZhuP
=+8/r
-----END PGP SIGNATURE-----
--
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/
^ permalink raw reply [flat|nested] 12+ messages in thread
* RE: "Hyperthreading" problems
@ 2004-12-28 22:53 Robb, Sam
0 siblings, 0 replies; 12+ messages in thread
From: Robb, Sam @ 2004-12-28 22:53 UTC (permalink / raw)
To: cygwin
> If you guys want cygwin to be used by real people, in real life
> production or development environments, you should go a bit
> further than
> "I don't have the problem on my computer, so fix it yourself".
OK. So, if he's unable to reproduce the problem, you want him
to... do what? Make random changes to try and fix things? How
is he supposed to know when he's fixed the problem if he can't
even manage to reproduce it in the first place?
> If you
> don't want to or are not able to pay attention to "real world" bugs,
> cygwin will probably never be more than an "almost working" program
> that runs on your computer the time to take nice screenshots,
> but fails
> miserably when users try to make it work in the real life.
I've been working for a company for three years now that relies
heavily on Cygwin as a foundation for commercial software. Our
internal build system is capable of compiling various products
under either Cygwin or Linux, all from the same set of makefiles
and scripts.
We'd hardly be able to do any of that if Cygwin was an "almost
working" program not ready for use in "real life." It is not
without it's problems - you've pointed out one. But overall,
Cygwin works, and it works well.
Why not get into the spirit of the season? 'Tis better to give
than to receive... PTC.
If you're unable to solve the problem yourself, then put a cash
value on your need to fix this bug, and hire someone to do it.
There are a lot of people that would *love* to pick up some
extra money around this time of year.
-Samrobb
--
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/
^ permalink raw reply [flat|nested] 12+ messages in thread
* RE: "Hyperthreading" problems
@ 2004-12-28 22:50 Bakken, Luke
0 siblings, 0 replies; 12+ messages in thread
From: Bakken, Luke @ 2004-12-28 22:50 UTC (permalink / raw)
To: Stephane Donze, cygwin
> multiprocessor machines and nobody seems to care about it. You cannot
> just expect people to "wait until you someday have a system
> that shows
> the problem" everytime they encounter a bug.
Actually since Cygwin is a free project this is a reasonable
expectation. If you want this fixed send the Cygwin developers a system
that reproduces this 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/
^ permalink raw reply [flat|nested] 12+ messages in thread
* "Hyperthreading" problems
@ 2004-12-24 8:01 Stéphane Donzé
2004-12-24 15:50 ` Christopher Faylor
0 siblings, 1 reply; 12+ messages in thread
From: Stéphane Donzé @ 2004-12-24 8:01 UTC (permalink / raw)
To: cygwin; +Cc: ncoghlan
[-- Attachment #1: Type: text/plain, Size: 1668 bytes --]
Hi,
we have encountered random hangs and crashes in cygwin (see output of
cygcheck attached to this message) on a dual-processor server running
Windows Server 2003. IMHO, the so-called "hyperthreading problems" reported
recently on this mailing list just have nothing to do with hyperthreading,
but are more generally related to multi-processor issues.
I used the following test (found on this mailing list archive, posted 6 Apr
2004 by Chuck McDevitt):
<QUOTE>
#! /bin/ksh
mypath=$(pwd)
while [[ ! -z $mypath ]]
do
mypath=$(pwd)
if [[ -z $mypath ]]
then
echo "Test Failed......Path is empty"
fi
done
in one shell, while running a large make in another, it will fail in a
variety of ways.
Under pdksh, it sometimes exits the test because "mypath" is empty, or it
core dumps, or hangs, or gives error messages.
Under bash, it hangs, crashes, or gives error messages (haven't seen it
exit the loop, but I didn't try long with bash).
By "hang", I mean the shell stops using CPU time, and become
non-responsive, and can only be stopped by killing the process.
The problem does not occur if hyperthreading is turned off.
</QUOTE>
When booting the server in single CPU (/ONECPU in boot.ini) the problem does
not appear.
More interesting, if I lock my bash session on a particular CPU by using
SetProcessAffinityMask, so that all child processes created by this shell
are locked on one CPU, the problem does not appear.
It seems that the bug has something to do with a same Cygwin process being
swapped from one CPU to another when running a piece of code that is not
locked properly (i.e. missing EnterCriticalSection or something like that).
Regards,
Stephane
[-- Attachment #2: cygcheck.out --]
[-- Type: application/octet-stream, Size: 25343 bytes --]
Cygwin Configuration Diagnostics
Current System Time: Fri Dec 24 08:49:15 2004
Windows .NET Server Ver 5.2 Build 3790
Path: \\turbocow\donze\bin\intel-win32
\\turbocow\donze\bin
e:\data\ng-src\donze\ng\bin
C:\apps\cygwin\bin
C:\apps\cygwin\usr\X11R6\bin
c:\WINNT\system32
c:\WINNT
c:\WINDOWS\system32
c:\WINDOWS
\\turbocow\ng\bin
c:\Program Files\Microsoft Visual Studio .NET 2003\Common7\IDE
c:\Program Files\Microsoft Visual Studio .NET 2003\VC7\bin
c:\Program Files\Microsoft Visual Studio .NET 2003\Common7\Tools\Bin
Output from C:\apps\cygwin\bin\id.exe (nontsec)
UID: 11115(donze) GID: 10513(Domain Users)
10513(Domain Users)
Output from C:\apps\cygwin\bin\id.exe (ntsec)
UID: 11115(donze) GID: 10513(Domain Users)
545(Users) 11128(Commercial) 11131(Developpeur)
10513(Domain Users) 15125(exalead) 13117(ng-bin)
15609(ng-dev) 11140(Terminal server)
SysDir: C:\WINDOWS\system32
WinDir: C:\WINDOWS
CYGWIN = `ntsec'
HOME = `\\turbocow\donze'
LD_LIBRARY_PATH = `\\turbocow\ng\lib\intel-win32:\ng\src\donze\ng\bin\intel-win32\exe'
MAKE_MODE = `unix'
PWD = `//turbocow/donze'
USER = `donze'
ALLUSERSPROFILE = `C:\Documents and Settings\All Users'
CLASSPATH = `/udir/donze/lib/intel-win32/rt.jar:/udir/donze/java:/ng/lib/crimson.jar:/ng/src/donze/ng/bin/intel-win32/corporate.jar'
CLUSTERLOG = `C:\WINDOWS\Cluster\cluster.log'
COMMONPROGRAMFILES = `C:\Program Files\Common Files'
COMPUTERNAME = `BLOO'
COMSPEC = `C:\WINDOWS\system32\cmd.exe'
CVSROOT = `/ng/cvs'
CVSUMASK = `7'
CVS_RSH = `/bin/ssh'
DISPLAY = `localhost:0.0'
EDITOR = `vi'
EXAOBJPATH = `//turbocow/ng/src/donze/ng/bin/exa2'
EXASRCPATH = `//turbocow/ng/src/donze/ng/src/exa/pkg;//turbocow/ng/donze/exa;//turbocow/ng/src/donze/config/src;//turbocow/ng/src/donze/tests'
HOMEPATH = `\\turbocow\donze'
HOSTNAME = `BLOO'
INCLUDE = `C:\Program Files\Microsoft Visual Studio .NET 2003\VC7\atlmfc\include;C:\Program Files\Microsoft SDK\include;C:\Program Files\Microsoft Visual Studio .NET 2003\VC7\include;C:\Program Files\Microsoft Visual Studio .NET 2003\VC7\PlatformSDK\include'
INFOPATH = `/usr/local/info:/usr/info:/usr/share/info:/usr/autotool/devel/info:/usr/autotool/stable/info:'
INTERIX_ROOT = `/dev/fs/C/SFU/'
INTERIX_ROOT_WIN = `C:\SFU\'
LIB = `C:\Program Files\Microsoft SDK\lib;C:\Program Files\Microsoft Visual Studio .NET 2003\VC7\lib'
LOGNAME = `donze'
LOGONSERVER = `\\MICROMOO'
MAIL = `/var/spool/mail/donze'
MANPATH = `/usr/man:/usr/local/man:/usr/share/man:/udir/donze/man'
NG = `debug-compile'
NGBIN = `/ng/src/donze/ng/bin'
NGCONFIG = `//turbocow/ng/src/donze/config/donze-win32.cfg'
NGLICENSE = `//turbocow/ng/src/donze/license.txt'
NGROOT = `/ng/src/donze/ng'
NUMBER_OF_PROCESSORS = `2'
OLDPWD = `//turbocow/donze'
OPENNT_ROOT = `/dev/fs/C/SFU/'
OS = `Windows_NT'
PATHEXT = `.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH'
PRINTER = `\\micromoo\Hop'
PROCESSOR_ARCHITECTURE = `x86'
PROCESSOR_IDENTIFIER = `x86 Family 6 Model 11 Stepping 1, GenuineIntel'
PROCESSOR_LEVEL = `6'
PROCESSOR_REVISION = `0b01'
PROGRAMFILES = `C:\Program Files'
PS1 = `\[\033]0;\h[\u]: \w\007\]\h\$ '
SFUDIR = `C:\SFU\'
SFUDIR_INTERIX = `/dev/fs/C/SFU/'
SHELL = `/bin/bash'
SHLVL = `1'
SSH_CLIENT = `192.168.204.63 52013 22'
SSH_CONNECTION = `192.168.204.63 52013 192.168.204.27 22'
SSH_TTY = `/dev/tty2'
SYSTEMDRIVE = `C:'
SYSTEMROOT = `C:\WINDOWS'
TEMP = `e:\tmp'
TERM = `xterm'
TMP = `c:\DOCUME~1\SSHD_S~1\LOCALS~1\Temp'
TZ = `RST-1RDT-2,M3.5.0/2,M10.5.0/3'
USERDOMAIN = `OFFICE'
USERNAME = `donze'
VS71COMNTOOLS = `C:\Program Files\Microsoft Visual Studio .NET 2003\Common7\Tools\'
WINDIR = `C:\WINDOWS'
XAPPLRESDIR = `/usr/X11R6/lib/X11/app-defaults'
XCMSDB = `/usr/X11R6/lib/X11/Xcms.txt'
XKEYSYMDB = `/usr/X11R6/lib/X11/XKeysymDB'
XNLSPATH = `/usr/X11R6/lib/X11/locale'
_ = `/usr/bin/cygcheck'
POSIXLY_CORRECT = `1'
HKEY_CURRENT_USER\Software\Cygnus Solutions
HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin
HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\mounts v2
(default) = `/cygdrive'
cygdrive flags = 0x00000022
HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\mounts v2\/
(default) = `C:\apps\cygwin'
flags = 0x00000002
HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\mounts v2\/ng
(default) = `\\turbocow\ng'
flags = 0x00000002
HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\mounts v2\/usr/bin
(default) = `C:\apps\cygwin/bin'
flags = 0x00000002
HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\mounts v2\/usr/lib
(default) = `C:\apps\cygwin/lib'
flags = 0x00000002
HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\Program Options
HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup
HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0
HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts
HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\00
(default) = `C:'
unix = `/'
fbinary = 0x00000000
fsilent = 0x00000000
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\MenuOrder\Start Menu\Programs\Cygnus Solutions
(default) = (unsupported type)
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2
(default) = `/cygdrive'
cygdrive flags = 0x00000022
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/
(default) = `C:\apps\cygwin'
flags = 0x0000000a
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/ng
(default) = `\\turbocow\ng'
flags = 0x0000000a
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/usr/bin
(default) = `C:\apps\cygwin/bin'
flags = 0x0000000a
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/usr/lib
(default) = `C:\apps\cygwin/lib'
flags = 0x0000000a
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\Program Options
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Terminal Server\Install\Software\Cygnus Solutions
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Terminal Server\Install\Software\Cygnus Solutions\Cygwin
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Terminal Server\Install\Software\Cygnus Solutions\Cygwin\mounts v2
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Terminal Server\Install\Software\Cygnus Solutions\Cygwin\Program Options
a: fd N/A N/A
c: hd NTFS 10236Mb 56% CP CS UN PA FC
d: hd N/A N/A
e: hd NTFS 34726Mb 2% CP CS UN PA FC New Volume
z: cd N/A N/A
C:\apps\cygwin / user binmode
\\turbocow\ng /ng user binmode
C:\apps\cygwin/bin /usr/bin user binmode
C:\apps\cygwin/lib /usr/lib user binmode
. /cygdrive user binmode,cygdrive
C:\apps\cygwin / system binmode
\\turbocow\ng /ng system binmode
C:\apps\cygwin/bin /usr/bin system binmode
C:\apps\cygwin/lib /usr/lib system binmode
. /cygdrive system binmode,cygdrive
Found: C:\apps\cygwin\bin\awk.exe
Found: C:\apps\cygwin\bin\bash.exe
Found: C:\apps\cygwin\bin\cat.exe
Found: C:\apps\cygwin\bin\cp.exe
Not Found: cpp (good!)
Found: C:\apps\cygwin\bin\find.exe
Not Found: gcc
Not Found: gdb
Found: C:\apps\cygwin\bin\grep.exe
Found: C:\apps\cygwin\bin\ld.exe
Found: C:\apps\cygwin\bin\ls.exe
Found: C:\apps\cygwin\bin\make.exe
Found: C:\apps\cygwin\bin\mv.exe
Found: C:\apps\cygwin\bin\rm.exe
Found: C:\apps\cygwin\bin\sed.exe
Found: C:\apps\cygwin\bin\sh.exe
Found: C:\apps\cygwin\bin\tar.exe
55k 2004/09/14 C:\apps\cygwin\bin\cygbz2-1.dll - os=4.0 img=1.0 sys=4.0
"cygbz2-1.dll" v0.0 ts=2004/9/14 6:16
18k 2004/07/06 C:\apps\cygwin\bin\cygcharset-1.dll - os=4.0 img=1.0 sys=4.0
"cygcharset-1.dll" v0.0 ts=2004/7/6 20:09
7k 2003/10/19 C:\apps\cygwin\bin\cygcrypt-0.dll - os=4.0 img=1.0 sys=4.0
"cygcrypt-0.dll" v0.0 ts=2003/10/19 9:57
846k 2004/12/11 C:\apps\cygwin\bin\cygcrypto-0.9.7.dll - os=4.0 img=1.0 sys=4.0
"cygcrypto-0.9.7.dll" v0.0 ts=2004/12/11 12:04
174k 2004/10/14 C:\apps\cygwin\bin\cygexpat-0.dll - os=4.0 img=1.0 sys=4.0
"cygexpat-0.dll" v0.0 ts=2004/10/14 10:34
129k 2004/03/11 C:\apps\cygwin\bin\cygfontconfig-1.dll - os=4.0 img=1.0 sys=4.0
"cygfontconfig-1.dll" v0.0 ts=2004/3/11 1:12
40k 2004/10/10 C:\apps\cygwin\bin\cygform-8.dll - os=4.0 img=1.0 sys=4.0
"cygform-8.dll" v0.0 ts=2004/10/10 10:33
45k 2001/04/25 C:\apps\cygwin\bin\cygform5.dll - os=4.0 img=1.0 sys=4.0
"cygform5.dll" v0.0 ts=2001/4/25 7:28
35k 2002/01/09 C:\apps\cygwin\bin\cygform6.dll - os=4.0 img=1.0 sys=4.0
"cygform6.dll" v0.0 ts=2002/1/9 7:03
48k 2003/08/09 C:\apps\cygwin\bin\cygform7.dll - os=4.0 img=1.0 sys=4.0
"cygform7.dll" v0.0 ts=2003/8/9 11:25
361k 2003/10/25 C:\apps\cygwin\bin\cygfreetype-6.dll - os=4.0 img=1.0 sys=4.0
"cygfreetype-6.dll" v0.0 ts=2003/10/22 6:18
28k 2003/07/20 C:\apps\cygwin\bin\cyggdbm-3.dll - os=4.0 img=1.0 sys=4.0
"cyggdbm-3.dll" v0.0 ts=2003/7/20 9:58
30k 2003/08/11 C:\apps\cygwin\bin\cyggdbm-4.dll - os=4.0 img=1.0 sys=4.0
"cyggdbm-4.dll" v0.0 ts=2003/8/11 4:12
19k 2003/03/22 C:\apps\cygwin\bin\cyggdbm.dll - os=4.0 img=1.0 sys=4.0
"cyggdbm.dll" v0.0 ts=2002/2/20 4:05
15k 2003/07/20 C:\apps\cygwin\bin\cyggdbm_compat-3.dll - os=4.0 img=1.0 sys=4.0
"cyggdbm_compat-3.dll" v0.0 ts=2003/7/20 10:00
15k 2003/08/11 C:\apps\cygwin\bin\cyggdbm_compat-4.dll - os=4.0 img=1.0 sys=4.0
"cyggdbm_compat-4.dll" v0.0 ts=2003/8/11 4:13
107k 2004/07/06 C:\apps\cygwin\bin\cyggettextlib-0-14-1.dll - os=4.0 img=1.0 sys=4.0
"cyggettextlib-0-14-1.dll" v0.0 ts=2004/7/6 19:56
17k 2004/07/06 C:\apps\cygwin\bin\cyggettextpo-0.dll - os=4.0 img=1.0 sys=4.0
"cyggettextpo-0.dll" v0.0 ts=2004/7/6 19:56
190k 2004/07/06 C:\apps\cygwin\bin\cyggettextsrc-0-14-1.dll - os=4.0 img=1.0 sys=4.0
"cyggettextsrc-0-14-1.dll" v0.0 ts=2004/7/6 19:56
17k 2001/06/28 C:\apps\cygwin\bin\cyghistory4.dll - os=4.0 img=1.0 sys=4.0
"cyghistory4.dll" v0.0 ts=2001/1/7 5:34
29k 2003/08/10 C:\apps\cygwin\bin\cyghistory5.dll - os=4.0 img=1.0 sys=4.0
"cyghistory5.dll" v0.0 ts=2003/8/11 1:16
25k 2004/10/12 C:\apps\cygwin\bin\cyghistory6.dll - os=4.0 img=1.0 sys=4.0
"cyghistory6.dll" v0.0 ts=2004/10/12 8:51
991k 2004/07/06 C:\apps\cygwin\bin\cygiconv-2.dll - os=4.0 img=1.0 sys=4.0
"cygiconv-2.dll" v0.0 ts=2004/7/6 20:10
22k 2001/12/13 C:\apps\cygwin\bin\cygintl-1.dll - os=4.0 img=1.0 sys=4.0
"cygintl-1.dll" v0.0 ts=2001/12/13 10:28
37k 2003/08/10 C:\apps\cygwin\bin\cygintl-2.dll - os=4.0 img=1.0 sys=4.0
"cygintl-2.dll" v0.0 ts=2003/8/10 23:50
54k 2004/07/06 C:\apps\cygwin\bin\cygintl-3.dll - os=4.0 img=1.0 sys=4.0
"cygintl-3.dll" v0.0 ts=2004/7/6 19:51
21k 2001/06/20 C:\apps\cygwin\bin\cygintl.dll - os=4.0 img=1.0 sys=4.0
"cygintl.dll" v0.0 ts=2001/6/20 19:09
132k 2003/08/11 C:\apps\cygwin\bin\cygjpeg-62.dll - os=4.0 img=1.0 sys=4.0
"cygjpeg-62.dll" v0.0 ts=2003/8/11 2:37
22k 2004/10/10 C:\apps\cygwin\bin\cygmenu-8.dll - os=4.0 img=1.0 sys=4.0
"cygmenu-8.dll" v0.0 ts=2004/10/10 10:33
26k 2001/04/25 C:\apps\cygwin\bin\cygmenu5.dll - os=4.0 img=1.0 sys=4.0
"cygmenu5.dll" v0.0 ts=2001/4/25 7:27
20k 2002/01/09 C:\apps\cygwin\bin\cygmenu6.dll - os=4.0 img=1.0 sys=4.0
"cygmenu6.dll" v0.0 ts=2002/1/9 7:03
29k 2003/08/09 C:\apps\cygwin\bin\cygmenu7.dll - os=4.0 img=1.0 sys=4.0
"cygmenu7.dll" v0.0 ts=2003/8/9 11:25
21k 2004/10/22 C:\apps\cygwin\bin\cygminires.dll - os=4.0 img=1.0 sys=4.0
"cygminires.dll" v0.0 ts=2004/10/22 22:28
74k 2004/10/10 C:\apps\cygwin\bin\cygncurses++-8.dll - os=4.0 img=1.0 sys=4.0
"cygncurses++-8.dll" v0.0 ts=2004/10/10 10:33
156k 2001/04/25 C:\apps\cygwin\bin\cygncurses++5.dll - os=4.0 img=1.0 sys=4.0
"cygncurses++5.dll" v0.0 ts=2001/4/25 7:29
175k 2002/01/09 C:\apps\cygwin\bin\cygncurses++6.dll - os=4.0 img=1.0 sys=4.0
"cygncurses++6.dll" v0.0 ts=2002/1/9 7:03
216k 2004/10/10 C:\apps\cygwin\bin\cygncurses-8.dll - os=4.0 img=1.0 sys=4.0
"cygncurses-8.dll" v0.0 ts=2004/10/10 10:25
226k 2001/04/25 C:\apps\cygwin\bin\cygncurses5.dll - os=4.0 img=1.0 sys=4.0
"cygncurses5.dll" v0.0 ts=2001/4/25 7:17
202k 2002/01/09 C:\apps\cygwin\bin\cygncurses6.dll - os=4.0 img=1.0 sys=4.0
"cygncurses6.dll" v0.0 ts=2002/1/9 7:03
224k 2003/08/09 C:\apps\cygwin\bin\cygncurses7.dll - os=4.0 img=1.0 sys=4.0
"cygncurses7.dll" v0.0 ts=2003/8/9 11:24
13k 2004/10/10 C:\apps\cygwin\bin\cygpanel-8.dll - os=4.0 img=1.0 sys=4.0
"cygpanel-8.dll" v0.0 ts=2004/10/10 10:32
15k 2001/04/25 C:\apps\cygwin\bin\cygpanel5.dll - os=4.0 img=1.0 sys=4.0
"cygpanel5.dll" v0.0 ts=2001/4/25 7:27
12k 2002/01/09 C:\apps\cygwin\bin\cygpanel6.dll - os=4.0 img=1.0 sys=4.0
"cygpanel6.dll" v0.0 ts=2002/1/9 7:03
19k 2003/08/09 C:\apps\cygwin\bin\cygpanel7.dll - os=4.0 img=1.0 sys=4.0
"cygpanel7.dll" v0.0 ts=2003/8/9 11:24
62k 2003/12/11 C:\apps\cygwin\bin\cygpcre-0.dll - os=4.0 img=1.0 sys=4.0
"cygpcre-0.dll" v0.0 ts=2003/12/11 18:01
63k 2003/04/11 C:\apps\cygwin\bin\cygpcre.dll - os=4.0 img=1.0 sys=4.0
"cygpcre.dll" v0.0 ts=2003/4/11 10:31
9k 2003/12/11 C:\apps\cygwin\bin\cygpcreposix-0.dll - os=4.0 img=1.0 sys=4.0
"cygpcreposix-0.dll" v0.0 ts=2003/12/11 18:01
61k 2003/04/11 C:\apps\cygwin\bin\cygpcreposix.dll - os=4.0 img=1.0 sys=4.0
"cygpcreposix.dll" v0.0 ts=2003/4/11 10:31
173k 2003/08/10 C:\apps\cygwin\bin\cygpng12.dll - os=4.0 img=1.0 sys=4.0
"cygpng12.dll" v0.0 ts=2003/8/11 0:35
22k 2002/06/09 C:\apps\cygwin\bin\cygpopt-0.dll - os=4.0 img=1.0 sys=4.0
"cygpopt-0.dll" v0.0 ts=2002/6/9 7:45
108k 2001/06/28 C:\apps\cygwin\bin\cygreadline4.dll - os=4.0 img=1.0 sys=4.0
"cygreadline4.dll" v0.0 ts=2001/1/7 5:34
148k 2003/08/10 C:\apps\cygwin\bin\cygreadline5.dll - os=4.0 img=1.0 sys=4.0
"cygreadline5.dll" v0.0 ts=2003/8/11 1:16
144k 2004/10/12 C:\apps\cygwin\bin\cygreadline6.dll - os=4.0 img=1.0 sys=4.0
"cygreadline6.dll" v0.0 ts=2004/10/12 8:51
171k 2004/12/11 C:\apps\cygwin\bin\cygssl-0.9.7.dll - os=4.0 img=1.0 sys=4.0
"cygssl-0.9.7.dll" v0.0 ts=2004/12/11 12:04
282k 2003/08/11 C:\apps\cygwin\bin\cygtiff4.dll - os=4.0 img=1.0 sys=4.0
"cygtiff4.dll" v0.0 ts=2003/8/11 4:32
27k 2004/03/05 C:\apps\cygwin\bin\cygungif-4.dll - os=4.0 img=1.0 sys=4.0
"cygungif-4.dll" v0.0 ts=2004/3/5 21:13
62k 2004/10/10 C:\apps\cygwin\bin\cygz.dll - os=4.0 img=1.0 sys=4.0
"cygz.dll" v0.0 ts=2004/10/10 6:09
1114k 2004/11/10 C:\apps\cygwin\bin\cygwin1.dll - os=4.0 img=1.0 sys=4.0
"cygwin1.dll" v0.0 ts=2004/11/10 14:34
Cygwin DLL version info:
DLL version: 1.5.12
DLL epoch: 19
DLL bad signal mask: 19005
DLL old termios: 5
DLL malloc env: 28
API major: 0
API minor: 116
Shared data: 4
DLL identifier: cygwin1
Mount registry: 2
Cygnus registry name: Cygnus Solutions
Cygwin registry name: Cygwin
Program options name: Program Options
Cygwin mount registry name: mounts v2
Cygdrive flags: cygdrive flags
Cygdrive prefix: cygdrive prefix
Cygdrive default prefix:
Build date: Wed Nov 10 08:34:47 EST 2004
Shared id: cygwin1S4
243k 2004/09/17 C:\apps\cygwin\usr\X11R6\bin\cygdps-1.dll - os=4.0 img=1.0 sys=4.0
"cygdps-1.dll" v0.0 ts=2004/9/17 11:48
26k 2004/09/17 C:\apps\cygwin\usr\X11R6\bin\cygdpstk-1.dll - os=4.0 img=1.0 sys=4.0
"cygdpstk-1.dll" v0.0 ts=2004/9/17 11:48
21k 2004/09/17 C:\apps\cygwin\usr\X11R6\bin\cygfontenc-1.dll - os=4.0 img=1.0 sys=4.0
"cygfontenc-1.dll" v0.0 ts=2004/9/17 11:53
36k 2004/09/17 C:\apps\cygwin\usr\X11R6\bin\cygFS-6.dll - os=4.0 img=1.0 sys=4.0
"cygFS-6.dll" v0.0 ts=2004/9/17 11:38
417k 2004/09/17 C:\apps\cygwin\usr\X11R6\bin\cygGL-1.dll - os=4.0 img=1.0 sys=4.0
"cygGL-1.dll" v0.0 ts=2004/9/17 11:45
439k 2004/09/17 C:\apps\cygwin\usr\X11R6\bin\cygGLU-1.dll - os=4.0 img=1.0 sys=4.0
"cygGLU-1.dll" v0.0 ts=2004/9/17 11:47
75k 2004/09/17 C:\apps\cygwin\usr\X11R6\bin\cygICE-6.dll - os=4.0 img=1.0 sys=4.0
"cygICE-6.dll" v0.0 ts=2004/9/17 11:30
9k 2004/09/17 C:\apps\cygwin\usr\X11R6\bin\cygoldX-6.dll - os=4.0 img=1.0 sys=4.0
"cygoldX-6.dll" v0.0 ts=2004/9/17 11:29
1416k 2004/09/17 C:\apps\cygwin\usr\X11R6\bin\cygOSMesa-4.dll - os=4.0 img=1.0 sys=4.0
"cygOSMesa-4.dll" v0.0 ts=2004/9/17 11:45
20k 2004/09/17 C:\apps\cygwin\usr\X11R6\bin\cygpsres-1.dll - os=4.0 img=1.0 sys=4.0
"cygpsres-1.dll" v0.0 ts=2004/9/17 11:49
30k 2004/09/17 C:\apps\cygwin\usr\X11R6\bin\cygSM-6.dll - os=4.0 img=1.0 sys=4.0
"cygSM-6.dll" v0.0 ts=2004/9/17 11:30
876k 2004/09/17 C:\apps\cygwin\usr\X11R6\bin\cygX11-6.dll - os=4.0 img=1.0 sys=4.0
"cygX11-6.dll" v0.0 ts=2004/9/17 11:29
253k 2004/09/17 C:\apps\cygwin\usr\X11R6\bin\cygXaw-6.dll - os=4.0 img=1.0 sys=4.0
"cygXaw-6.dll" v0.0 ts=2004/9/17 11:34
356k 2004/09/17 C:\apps\cygwin\usr\X11R6\bin\cygXaw-7.dll - os=4.0 img=1.0 sys=4.0
"cygXaw-7.dll" v0.0 ts=2004/9/17 11:36
362k 2004/09/17 C:\apps\cygwin\usr\X11R6\bin\cygXaw-8.dll - os=4.0 img=1.0 sys=4.0
"cygXaw-8.dll" v0.0 ts=2004/9/17 11:37
275k 2004/01/13 C:\apps\cygwin\usr\X11R6\bin\cygXaw3d-7.dll - os=4.0 img=1.0 sys=4.0
"cygXaw3d-7.dll" v0.0 ts=2004/1/13 23:17
9k 2004/09/17 C:\apps\cygwin\usr\X11R6\bin\cygXcomposite-1.dll - os=4.0 img=1.0 sys=4.0
"cygXcomposite-1.dll" v0.0 ts=2004/9/17 11:51
30k 2004/09/17 C:\apps\cygwin\usr\X11R6\bin\cygXcursor-1.dll - os=4.0 img=1.0 sys=4.0
"cygXcursor-1.dll" v0.0 ts=2004/9/17 11:50
9k 2004/09/17 C:\apps\cygwin\usr\X11R6\bin\cygXdamage-1.dll - os=4.0 img=1.0 sys=4.0
"cygXdamage-1.dll" v0.0 ts=2004/9/17 11:51
7k 2004/09/17 C:\apps\cygwin\usr\X11R6\bin\cygXevie-1.dll - os=4.0 img=1.0 sys=4.0
"cygXevie-1.dll" v0.0 ts=2004/9/17 11:51
49k 2004/09/17 C:\apps\cygwin\usr\X11R6\bin\cygXext-6.dll - os=4.0 img=1.0 sys=4.0
"cygXext-6.dll" v0.0 ts=2004/9/17 11:30
16k 2004/09/17 C:\apps\cygwin\usr\X11R6\bin\cygXfixes-3.dll - os=4.0 img=1.0 sys=4.0
"cygXfixes-3.dll" v0.0 ts=2004/9/17 11:51
56k 2004/03/11 C:\apps\cygwin\usr\X11R6\bin\cygXft-1.dll - os=4.0 img=1.0 sys=4.0
"cygXft-1.dll" v0.0 ts=2003/11/18 2:42
63k 2004/03/23 C:\apps\cygwin\usr\X11R6\bin\cygXft-2.dll - os=4.0 img=1.0 sys=4.0
"cygXft-2.dll" v0.0 ts=2004/3/23 23:20
27k 2004/09/17 C:\apps\cygwin\usr\X11R6\bin\cygXi-6.dll - os=4.0 img=1.0 sys=4.0
"cygXi-6.dll" v0.0 ts=2004/9/17 11:37
125k 2004/09/17 C:\apps\cygwin\usr\X11R6\bin\cygxkbfile-1.dll - os=4.0 img=1.0 sys=4.0
"cygxkbfile-1.dll" v0.0 ts=2004/9/17 11:38
12k 2004/09/17 C:\apps\cygwin\usr\X11R6\bin\cygxkbui-1.dll - os=4.0 img=1.0 sys=4.0
"cygxkbui-1.dll" v0.0 ts=2004/9/17 11:38
76k 2004/09/17 C:\apps\cygwin\usr\X11R6\bin\cygXmu-6.dll - os=4.0 img=1.0 sys=4.0
"cygXmu-6.dll" v0.0 ts=2004/9/17 11:32
11k 2004/09/17 C:\apps\cygwin\usr\X11R6\bin\cygXmuu-1.dll - os=4.0 img=1.0 sys=4.0
"cygXmuu-1.dll" v0.0 ts=2004/9/17 11:32
26k 2004/09/17 C:\apps\cygwin\usr\X11R6\bin\cygXp-6.dll - os=4.0 img=1.0 sys=4.0
"cygXp-6.dll" v0.0 ts=2004/9/17 11:33
51k 2004/09/17 C:\apps\cygwin\usr\X11R6\bin\cygXpm-4.dll - os=4.0 img=1.0 sys=4.0
"cygXpm-4.dll" v0.0 ts=2004/9/17 11:33
11k 2004/09/17 C:\apps\cygwin\usr\X11R6\bin\cygXrandr-2.dll - os=4.0 img=1.0 sys=4.0
"cygXrandr-2.dll" v0.0 ts=2004/9/17 11:50
28k 2004/09/17 C:\apps\cygwin\usr\X11R6\bin\cygXrender-1.dll - os=4.0 img=1.0 sys=4.0
"cygXrender-1.dll" v0.0 ts=2004/9/17 11:49
8k 2004/09/17 C:\apps\cygwin\usr\X11R6\bin\cygXRes-1.dll - os=4.0 img=1.0 sys=4.0
"cygXRes-1.dll" v0.0 ts=2004/9/17 11:50
282k 2004/09/17 C:\apps\cygwin\usr\X11R6\bin\cygXt-6.dll - os=4.0 img=1.0 sys=4.0
"cygXt-6.dll" v0.0 ts=2004/9/17 11:32
27k 2004/09/17 C:\apps\cygwin\usr\X11R6\bin\cygXTrap-6.dll - os=4.0 img=1.0 sys=4.0
"cygXTrap-6.dll" v0.0 ts=2004/9/17 11:50
17k 2004/09/17 C:\apps\cygwin\usr\X11R6\bin\cygXtst-6.dll - os=4.0 img=1.0 sys=4.0
"cygXtst-6.dll" v0.0 ts=2004/9/17 11:37
Cygwin Package Information
Last downloaded files to: C:\apps\cygwin\pkg
Last downloaded files from: ftp://ftp.easynet.be/cygwin
Package Version
_update-info-dir 00230-1
ash 20040127-1
base-files 3.1-4
base-passwd 2.1-1
bash 2.05b-16
binutils 20040725-2
bzip2 1.0.2-6
coreutils 5.2.1-2
crypt 1.1-1
ctags 5.5-4
cygrunsrv 1.0-1
cygutils 1.2.5-1
cygwin 1.5.12-1
cygwin-doc 1.3-7
diffutils 2.8.7-1
editrights 1.01-1
emacs 21.2-13
emacs-X11 21.2-13
expat 1.95.8-1
fileutils 4.1-3
findutils 4.2.10-5
fontconfig 2.2.2-1
freetype2 2.1.5-1
gawk 3.1.4-3
gdbm 1.8.3-7
gettext 0.14.1-1
grep 2.5-1
groff 1.18.1-2
gzip 1.3.5-1
less 381-1
libbz2_1 1.0.2-6
libcharset1 1.9.2-1
libfontconfig1 2.2.2-1
libfreetype26 2.1.5-1
libgdbm 1.8.0-5
libgdbm-devel 1.8.3-7
libgdbm3 1.8.3-3
libgdbm4 1.8.3-7
libgettextpo0 0.14.1-1
libiconv 1.9.2-1
libiconv2 1.9.2-1
libintl 0.10.38-3
libintl1 0.10.40-1
libintl2 0.12.1-3
libintl3 0.14.1-1
libjpeg62 6b-11
libncurses5 5.2-1
libncurses6 5.2-8
libncurses7 5.3-4
libncurses8 5.4-1
libpcre 4.1-1
libpcre0 4.5-1
libpng12 1.2.5-4
libpopt0 1.6.4-4
libreadline4 4.1-2
libreadline5 4.3-5
libreadline6 5.0-1
libtiff4 3.6.0-5
libungif 4.1.0-3
libXft 2.1.6-1
libXft1 1.0.0-1
libXft2 2.1.6-1
links 0.99pre14-1
login 1.9-7
lynx 2.8.4-8
make 3.80-1
man 1.5o1-1
minires 1.00-1
mktemp 1.5-3
more 2.11o-1
ncftp 3.1.7-1
ncurses 5.4-1
openssh 3.9p1-2
openssl 0.9.7e-1
pcre 4.5-1
pcre-doc 4.5-1
pdksh 5.2.14-3
readline 5.0-1
rsync 2.6.3-1
sed 4.1.2-1
sh-utils 2.0.15-5
tar 1.13.25-5
termcap 20021106-2
terminfo 5.4_20041009-1
texinfo 4.2-4
textutils 2.0.21-2
unzip 5.50-5
vim 6.3-1
wget 1.9.1-1
which 1.5-2
X-startup-scripts 1.0.10-2
Xaw3d 1.5D-5
xorg-x11-base 6.8.1.0-1
xorg-x11-bin 6.8.1.0-2
xorg-x11-bin-dlls 6.8.1.0-1
xorg-x11-bin-lndir 6.8.1.0-1
xorg-x11-etc 6.8.1.0-1
xorg-x11-fenc 6.8.1.0-2
xorg-x11-fnts 6.8.1.0-3
xorg-x11-libs-data 6.8.1.0-1
xorg-x11-xwin 6.8.1.0-8
xterm 196-1
zip 2.3-6
zlib 1.2.2-1
Use -h to see help about each section
[-- Attachment #3: Type: text/plain, Size: 218 bytes --]
--
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/
^ permalink raw reply [flat|nested] 12+ messages in thread* Re: "Hyperthreading" problems
2004-12-24 8:01 Stéphane Donzé
@ 2004-12-24 15:50 ` Christopher Faylor
0 siblings, 0 replies; 12+ messages in thread
From: Christopher Faylor @ 2004-12-24 15:50 UTC (permalink / raw)
To: cygwin
On Fri, Dec 24, 2004 at 09:01:17AM +0100, St?phane Donz? wrote:
>we have encountered random hangs and crashes in cygwin (see output of
>cygcheck attached to this message) on a dual-processor server running
>Windows Server 2003. IMHO, the so-called "hyperthreading problems" reported
>recently on this mailing list just have nothing to do with hyperthreading,
>but are more generally related to multi-processor issues.
If you have followed the thread, then you know that I have a multi-processor
system and I don't have the problem.
>I used the following test (found on this mailing list archive, posted 6 Apr
>2004 by Chuck McDevitt):
>
><QUOTE>
>
>#! /bin/ksh
>mypath=$(pwd)
>while [[ ! -z $mypath ]]
>do
> mypath=$(pwd)
> if [[ -z $mypath ]]
> then
> echo "Test Failed......Path is empty"
> fi
>done
There is no point in reposting scripts. There is no point in
recapitulating the problem. There is no point in making obvious
observations about what one would suspect the cause would be without
bothering to look at the code.
Your options are to fix the problem yourself or wait until I someday
have a system which demonstrates the problem.
cgf
--
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/
^ permalink raw reply [flat|nested] 12+ messages in thread
end of thread, other threads:[~2005-01-02 19:19 UTC | newest]
Thread overview: 12+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <41D1D2B2.4030200@exalead.com>
2004-12-28 22:29 ` "Hyperthreading" problems Stephane Donze
2004-12-28 23:15 ` Christopher Faylor
2004-12-29 0:50 ` Brian Bruns
2005-01-01 21:07 ` Stephane Donze
2005-01-02 19:19 ` Larry Hall
2004-12-29 1:26 ` Brian Dessent
2004-12-29 1:51 ` Christopher Faylor
2004-12-29 15:33 ` Volker Bandke
2004-12-28 22:53 Robb, Sam
-- strict thread matches above, loose matches on Subject: below --
2004-12-28 22:50 Bakken, Luke
2004-12-24 8:01 Stéphane Donzé
2004-12-24 15:50 ` Christopher Faylor
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).