summaryrefslogtreecommitdiffstats
path: root/ChangeLog
diff options
context:
space:
mode:
authorRainer Gerhards <rgerhards@adiscon.com>2008-09-30 10:58:39 +0200
committerRainer Gerhards <rgerhards@adiscon.com>2008-09-30 10:58:39 +0200
commit4026000efcc736d1931785e4fa3c1fd21258fd95 (patch)
tree198d8d2529552ef177ce22a65552ce699753a92e /ChangeLog
parent658130c083b82d129f108074070e2aa198f6fa59 (diff)
parent92c2e09d19bef9dd10d2e85a663925124d6e00e4 (diff)
downloadrsyslog-4026000efcc736d1931785e4fa3c1fd21258fd95.tar.gz
rsyslog-4026000efcc736d1931785e4fa3c1fd21258fd95.tar.xz
rsyslog-4026000efcc736d1931785e4fa3c1fd21258fd95.zip
Merge branch 'helgrind'v3.21.5
Conflicts: ChangeLog
Diffstat (limited to 'ChangeLog')
-rw-r--r--ChangeLog9
1 files changed, 9 insertions, 0 deletions
diff --git a/ChangeLog b/ChangeLog
index a8dd113b..76791182 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -14,6 +14,15 @@ Version 3.21.5 [DEVEL] (rgerhards), 2008-09-30
- imported a number of fixes and enhancements from the stable and
devel branches, including a fix to a potential segfault on HUP
when using UDP listners
+- re-enabled gcc builtin atomic operations and added a proper
+ ./configure check
+- bugfix: potential race condition when adding messages to queue
+ There was a wrong order of mutex lock operations. It is hard to
+ believe that really caused problems, but in theory it could and with
+ threading we often see that theory becomes practice if something is only
+ used long enough on a fast enough machine with enough CPUs ;)
+- cleaned up internal debug system code and made it behave better
+ in regard to multi-threading
---------------------------------------------------------------------------
Version 3.21.4 [DEVEL] (rgerhards), 2008-09-04
- removed compile time fixed message size limit (was 2K), limit can now