But, then it's been theorized that I am rather incompetent about testing
these things,
preferring to test in a magical "It always works" type of
environment that is loaded with super special software. That's why
I need something like the stack dump from normal folks who don't have
access to all o
Is it me or is the cygwin1.dll becoming more unstable each passing day?
-marcus
Hi Chris,
I've test the lastest snapshot (14th Dec II) with the ThreadTest,
the new problems have been resolved, still the old ones remain.
thanx for the quick fix.
Regards
Arash Partow
__
Hi Philippe,
I've tested the latest dll snapshot (12/12), and its still displaying the
problem.
nothing was changed in the signaling or pthreads area that would
effect the problem.
maybe try using the provided snapshot perhaps?
-Marcus
Hi all!
I've tested the latest CVS version (2003-12-12 1
chris,
Let me say it again: I don't see the problem either with my changes or
without it. I just didn't see any good reason to go on creating threads
after a signal has been received which the original code did.
I agree with you totally, it would be reasonable for the garbage collector
thing to
chris,
i tried the code you provided, it does resolve the issue, however why do
we need to change the test? as arash pointed out it seems to work on other
platforms well enough. the modified version arash posted back seems to
demonstrate the problem, and all it seems he has done get rid of delays
Hi Chris,
I've tried the latest snapshot 8/12/2003, that dll doesn't seem to
have the win32-hndl problem that was seen in previous versions of
the dll, but it is still exibiting the signalling problems.
Marcus
I fixed a handle leak problem last night. I don't suppose that it
occurred to you
Hi Arash,
I've downloaded the tests and dlls both from you're site and last
few cygwin snapshots and CONFIRMED your results. There is a major
bug in both the signaling during threads and also the problem
of accumulating handles. Just by looking at the various changes
in the snapshots it seems cgf
Hi Arash,
I've built the cygwin1.dll with debugging info off, and I have
been able to replicate your problem. It seems to be comeing from
inside the string allocator in stl but a more deeper anlysis
shows the problem to be coming from the i386 memcpy, i don't
think the memcpy has been written prop
Hi
I tested your program and found out that the crashes were in compiler
generated code (especially in STL code). Upgrading to the latest version
of everything (GCC in particular) solved everything for me without using
any Cygwin snapshots.
I've found that it crashes too, I've tried compili
9 matches
Mail list logo
