Please send questions regarding Cygwin to the cygwin mailing list. There
you will get the expertise of the whole community rather than that of just
one individual. Also, replies can be archived for others to search in the
future. As such, I have redirected the discussion there. Thanks.
On
On Tue, 2 Dec 2003, Christopher Faylor wrote:
On Tue, Dec 02, 2003 at 10:42:38AM -0600, Brian Ford wrote:
Thomas Pfaff's 2003-12-01 pthread change might have fixed it.
I don't see why it would. bash doesn't use pthreads, AFAIK.
Sorry, I still need to learn not to say stupid speculative
Brian Ford wrote:
On Tue, 2 Dec 2003, Christopher Faylor wrote:
On Tue, Dec 02, 2003 at 10:42:38AM -0600, Brian Ford wrote:
Could you try a snapshot that includes it?
FWIW, I ran the test case overnight on my old 450 MHz Pentium Pro SGI 320
running NT4, all packages up-to-date, and a cvs
On Wed, 3 Dec 2003, Antoine Labour wrote:
Brian Ford wrote:
On Tue, Dec 02, 2003 at 10:42:38AM -0600, Brian Ford wrote:
Could you try a snapshot that includes it?
FWIW, I ran the test case overnight on my old 450 MHz Pentium Pro SGI 320
running NT4, all packages up-to-date, and a cvs
Please use cygwin at cygwin dot com for cygwin-related mail. I have set the
reply-to header for your convenience.
On Mon, Dec 01, 2003 at 12:24:47PM -0800, Antoine Labour wrote:
Ronald Landheer-Cieslak wrote:
Unfortunately, I don't have any system with more than one CPU, so there's
no way I
On Tue, 2 Dec 2003, Ronald Landheer-Cieslak wrote:
On Mon, Dec 01, 2003 at 12:24:47PM -0800, Antoine Labour wrote:
Ronald Landheer-Cieslak wrote:
Unfortunately, I don't have any system with more than one CPU, so there's
no way I can test it on a system like that and I have not run into any
On Tue, Dec 02, 2003 at 10:42:38AM -0600, Brian Ford wrote:
On Tue, 2 Dec 2003, Ronald Landheer-Cieslak wrote:
On Mon, Dec 01, 2003 at 12:24:47PM -0800, Antoine Labour wrote:
Ronald Landheer-Cieslak wrote:
Unfortunately, I don't have any system with more than one CPU, so there's
no way I
Nicholas Wourms wrote:
news.gmane.org wrote:
I'm running in concurrences 5 complex bash batch, and sometimes (2
times on
3) one or more (very rarely) batch stop to do something. I've put a
lot of
trace to see where is the problem, but seems rarely arrived at the
same line
of code.
I've also
Unfortunately, I don't have any system with more than one CPU, so there's no
way I can test it on a system like that and I have not run into any similar
problems on any of the systems I have.. (Cygwin or otherwise).
I'm afraid someone else will have to debug this, as I don't see that I can
do
news.gmane.org wrote:
I'm running in concurrences 5 complex bash batch, and sometimes (2 times on
3) one or more (very rarely) batch stop to do something. I've put a lot of
trace to see where is the problem, but seems rarely arrived at the same line
of code.
I've also tried to use strace tool,
10 matches
Mail list logo
