This is the mail archive of the cygwin mailing list for the Cygwin project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
On Feb 9 15:06, Steven Bardwell wrote: > > How do you test that? You're calling fcntl(F_SETLKW) exactly once at > > the start of your test application, but never again later. We're > > talking advisory file locking here, so, where's the next fcntl call > > waiting for the lock? > > > > I debugged your test app and the lock still exists after the spawn call. > > > > > > > > Corinna > > To test this, I start this program to check for the lock: Ok, I can reproduce it, but it's too late to debug this today. I have to say, though, that fcntl advisory locking is POSIX functionality, while the spawn functions are not. In fact these dreaded spawn entry points are rather old stuff, which hasn't been tested for a long time. FWIW, advisory file locking has never been tested with them, and the fact that it doesn't work as expected doesn't exactly disturb me. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat
Attachment:
pgpp4EHo5OBqL.pgp
Description: PGP signature
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |