P.S.: I presume the fix will show up in the next Cygwin release.
Nope. It's just for you. No one else is privileged enough to get the
fix. :-)
:-))
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation:
Hi Christopher,
How about today's snapshot? Corinna has YA told me what I did wrong with the
latest round of spinlock changes and today's snapshot reflects her obvious
fix.
Good news for the weekend! I've been running my original scenario with
20100318 repeatedly all day long. I couldn't
Hi Corinna,
Would you mind to give the latest developer snapshot from
http://www.cygwin.com/snapshots/ a try? It tries very carefully to
eliminate concurrency problems in the initialization phase.
I see. With the same scenario as in my original posting I trigger an
assertion added by
Hi Christopher,
Please find attached the requested information. However I had to edit
it - as carefully as possible - to omit hints on the SAP-internal IT
infrastructure.
Thanks. It would be nice if we could come up with some way to make
cygcheck not output sensitive information but I doubt
Hi Christopher,
Is echo being run under a bash shell? From the command prompt? In a
.bat file? Repeatedly in a loop?
I experienced it in the same scenario described in my original report:
A non-Cygwin shell calling a non-Cygwin 'gnumake -j' processing Makefiles
with rules calling Cygwin
Hi Corinna,
Are you absolutely sure that you can rule out BLODA effects?
I found and read http://cygwin.com/faq/faq.using.html#faq.using.bloda.
I can _NOT_ rule out those effects at all. In the opposite I know that I
run such software and I have sporadic file access problems (as described)
Hi,
Does the patch help?
As the issue is sporadic it's not that easy to come up with a conclusive
answer...
I downloaded http://cygwin.com/snapshots/cygwin1-20100309.dll.bz2,
unpacked and renamed the DLL and used it as drop-in replacement to the
1.7.1 DLL.
I experienced three times by now
Hi Corrina,
Does the patch help?
I've right now no access to my dev box. I'll be able to
provide feedback (either positive or negative) tomorrow...
Regards, Oliver
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation:
Hi Corrina,
Thanks for your involvement :-)
[...] a spinlock [...] With
InterlockedCompareExchange() and Sleep() it should be quite simple to
create one that's very efficient in the usual scenario.
Does the below patch fix this for you?
I'll test the snapshot asap!
[...]
+ LONG init
Hi,
I'll test the snapshot asap!
The final patch is from cgf. It's probably more performant since it
drops the requirement for an additional spinlock.
The snapshot contains try #3 on getting the locking right.
Thank you both for clarifying. I was already aware of that by browsing
through the
Hi Christopher,
Fist of all thanks for your immediate feedback :-)
/* Initialize installation root dir. */
if (!installation_root[0])
init_installation_root ();
I'll check in something tonight which attempts to solve this problem.
Thanks in advance.
It's a somewhat tricky
Hi,
I think Cygwin 1.7 has a concurrency issue with the shared state initialization
- which we experience because we use Cygwin in a probably untypical fashion:
We call from a non-Cygwin shell a non-Cygwin gnumake. The Makefile rules mostly
call a non-Cygwin C compiler and linker. However
12 matches
Mail list logo
