update compat

[lttv.git] / doc / developer / lttng-lttv-compatibility.html

diff --git a/doc/developer/lttng-lttv-compatibility.html b/doc/developer/lttng-lttv-compatibility.html
index 4a13826ff5080a5e0f72ba79ecaab213773cf88e..ab4cb738d4435d80576667b54a91ddd13f0c8bf0 100644 (file)
--- a/doc/developer/lttng-lttv-compatibility.html
+++ b/doc/developer/lttng-lttv-compatibility.html
@@ -3809,6 +3809,7 @@ powerpc64, s390, sparc, sparc64.<br>
 0.12.31<br>
 0.12.32<br>
 0.12.33<br>
+0.12.34<br>
 </td>
 <td style="vertical-align: top;">
 0.191<br>
@@ -3841,6 +3842,8 @@ powerpc64, s390, sparc, sparc64.<br>
 0.218<br>
 0.219<br>
 0.220<br>
+0.221<br>
+0.222<br>
 </td>
 <td style="vertical-align: top;">
 0.76<br>
@@ -3877,6 +3880,7 @@ obsolete<br>
 2.6.33.3<br>
 2.6.33.4<br>
 2.6.34<br>
+2.6.34.4<br>
 </td>
 <td style="vertical-align: top;">
 LTTng 0.191, LTTV 0.12.30 coming with trace format 2.6 revert to the pre-2.4
@@ -3956,6 +3960,13 @@ LTTng 0.219 fixes an out-of-bound array use in marker.c.<br>
 LTTng 0.220 forces alignment on 128 bytes (larger than structure) to ensure that
 the section alignment in the linker script matches that of overly enthusiastic
 compilers.<br>
+LTTV 0.12.34 fixes a bug in string handling in libltttraceread. Caused incorrect
+string length calculation when a string appeared in many per-cpu tracefiles of
+the same channel.<br>
+LTTng 0.221 now supports writing strings into the buffer when string input is
+being modified concurrently. Such a race should not render the trace
+unreadable.<br>
+LTTng 0.222 supports kernel 2.6.34.4.<br>
 </td>
 <td style="vertical-align: top;">
 </td>