Browse source

Changelog

Query
From:
To:
Branch:
Path:
Message:
BugID:
User: +
Format:
: 3 checkins (+2/-1) by Henrik Grubbström (Grubba) <grubba@grubba.org> : 0 checkins (+0/-0) by 0 people : 0 checkins (+0/-0) by 0 people : 3 checkins (+6/-1) by Henrik Grubbström (Grubba) <grubba@grubba.org> Lines added/removed recently

Thursday 01 November 2018

2018-11-01 13:40:46 (1 year ago) by Henrik Grubbström (Grubba) <grubba@grubba.org>

Merge branch 'patches/pike140' into 8.0

* patches/pike140:
Thread.Queue [Paranoia]: Attempt to work around glibc bugs.
Merge branch 'patches/pike140' into 8.1

* patches/pike140:
Thread.Queue [Paranoia]: Attempt to work around glibc bugs.

2018-11-01 13:35:24 (1 year ago) by Henrik Grubbström (Grubba) <grubba@grubba.org>

Thread.Queue [Paranoia]: Attempt to work around glibc bugs.

Glibc 2.24 and earlier have a broken implementation of condition
variables (cf https://sourceware.org/bugzilla/show_bug.cgi?id=13165).

Attempt to work around the issue by having the signalling thread
release the associated mutex before signalling.

Potential fix for [Pike-140].

Monday 29 October 2018

2018-10-29 13:12:35 (1 year ago) by Henrik Grubbström (Grubba) <grubba@grubba.org>

Merge branch 'patches/pike140' into 8.0

* patches/pike140:
Thread.Queue [Paranoia]: Broadcast the changed state.
Merge branch 'patches/pike140' into 8.1

* patches/pike140:
Thread.Queue [Paranoia]: Broadcast the changed state.

2018-10-29 13:03:33 (1 year ago) by Henrik Grubbström (Grubba) <grubba@grubba.org>

Thread.Queue [Paranoia]: Broadcast the changed state.

This is intended to ensure that the state-changed signal
is not lost.

Consider the case when there is a thread that listens on the
condition, but does not act on it; it could starve the threads
that do intend to act on it.

Fixes PIKE-140 (#8140).

[permalink]

Bugs mentioned

  #8140CLOSEDIncrease thread-paranoia in Thread.Queue
Bugs? Suggestions?