On 2015-02-24 Corinna Vinschen wrote:
> On Feb 24 16:16, Lasse Collin wrote:
> > I'm going to release xz 5.2.1 in a day or two. Should that release
> > have a workaround for this Cygwin bug? The workaround would avoid
> > using O_NONBLOCK on stdout. It adds a race condit
On 2015-02-24 Corinna Vinschen wrote:
> On Feb 24 15:54, Lasse Collin wrote:
> > Many other pthread functions are similar in sense that they must
> > never return EINTR. A bug similar to the one in pthread::join exist
> > in pthread_mutex::lock. If SA_RESTART isn
On 2015-02-24 Corinna Vinschen wrote:
> On Feb 24 08:16, Thomas Wolff wrote:
> > Am 23.02.2015 um 13:23 schrieb Corinna Vinschen:
> > >On Feb 23 11:56, Corinna Vinschen wrote:
> > >>On Feb 22 22:07, Lasse Collin wrote:
> > >>>Alternative idea: Wo
d_mutex::lock. If SA_RESTART isn't used, signals can make
multiple threads get a lock on the same mutex at the same time. A test
program is attached. Adding cw_sig_restart to the cygwait call in
pthread_mutex::lock fixes this.
--
Lasse Collin | IRC: Larhzu @ IRCnet & Freenode
// gcc -std
handling the return value assumes that only WAIT_OBJECT_0 and
WAIT_CANCELED are possible. The default section of the switch statement
has a comment "should never happen" and it returns EINVAL. It might be
that the problem occurs only when SA_RESTART isn't used.
--
Lasse Collin
(I have now subscribed to the list to get everyone's replies. Sorry for
breaking the message thread.)
Eric Blake wrote:
> On 02/20/2015 01:21 PM, Lasse Collin wrote:
> > The above Cygwin behavior would make it very easy to add a
> > workaround to xz for the pipe-data-loss p
the workaround idea will
cause trouble in the future when the bug in Cygwin gets fixed.
--
Lasse Collin | IRC: Larhzu @ IRCnet & Freenode
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
.0, I investigated that first. There also seems to be something
wrong with xz 5.2.0 in threaded mode under Cygwin which needs more
investigation (random pthread_join() failures cause assertion failures
if xz was built with --enable-debug).
--
Lasse Collin | IRC: Larhzu @ IRCnet & Freenode
// gcc -
On 2013-11-26 Denis Excoffier wrote:
> On 2013-11-25 à 21:58 +02:00, Lasse Collin wrote:
> > If you haven't already tried, please compile both 5.1.2alpha and
> > 5.1.3alpha from source while keeping everything else unchanged, and
> > see if the bug really only occurs
gwin or Windows.
If you haven't already tried, please compile both 5.1.2alpha and
5.1.3alpha from source while keeping everything else unchanged, and see
if the bug really only occurs with 5.1.3alpha.
--
Lasse Collin | IRC: Larhzu @ IRCnet & Freenode
--
Problem reports:
ions: http://php.net/manual/en/ref.exec.php
--
/Lasse
--
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/
evement of cygwin?
It emulates UNIX under Windows.
/Lasse
--
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/
Question NS wrote:
[SNIP]
You're not by any chance using make with the -j option, are you?
/Lasse
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.htm
Igor Pechtchanski wrote:
[SNIP]
(parens are optional,
Not in the coding guidelines at work... :-)
but the main thing is that there can't be a comma
after FH in the print statement).
Oops, yes that's correct... :-)
--
/Lasse
--
Unsubscribe info: http://cygwin.com/ml/#u
/search?q=perl+piped+open
--
/Lasse
--
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/
there is no distinction in Windows between the meta data and the file.
If the file is locked, the meta data is too and vice versa. So a locked
file tells you nothing about the existence of ACLs on this file.
See my other post in this thread.
--
/Lasse
--
Unsubscribe info: http://cy
er the result of this discussion is, the most important part is,
that the failing call to acl() shouldn't result in ls printing an error
message in this case.
Agreed.
/Lasse
--
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/
t "there's more to it than what is
shown" and I think that would be right thing to convey for busy files.
I think this behaviour would be the least surprising...
--
/Lasse
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com
t sure what to do about that...
But at least it builds now.. ;-)
--
/Lasse
--
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/
19 matches
Mail list logo