X-Git-Url: http://git.liburcu.org/?a=blobdiff_plain;f=doc%2Fdeveloper%2Flttng-lttv-compatibility.html;h=4677f6c4253d61ace87b1e7427994bb1811af222;hb=b72282a64f7788287332b6a95cf3ce0f7dd96d8a;hp=4a13826ff5080a5e0f72ba79ecaab213773cf88e;hpb=309d9cfeb22671401ed94c1686084d650594c3c8;p=lttv.git diff --git a/doc/developer/lttng-lttv-compatibility.html b/doc/developer/lttng-lttv-compatibility.html index 4a13826f..4677f6c4 100644 --- a/doc/developer/lttng-lttv-compatibility.html +++ b/doc/developer/lttng-lttv-compatibility.html @@ -3809,6 +3809,8 @@ powerpc64, s390, sparc, sparc64.
0.12.31
0.12.32
0.12.33
+0.12.34
+0.12.35
0.191
@@ -3841,6 +3843,9 @@ powerpc64, s390, sparc, sparc64.
0.218
0.219
0.220
+0.221
+0.222
+0.223
0.76
@@ -3877,6 +3882,8 @@ obsolete
2.6.33.3
2.6.33.4
2.6.34
+2.6.34.4
+2.6.35.2
LTTng 0.191, LTTV 0.12.30 coming with trace format 2.6 revert to the pre-2.4 @@ -3956,6 +3963,19 @@ LTTng 0.219 fixes an out-of-bound array use in marker.c.
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.
+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.
+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.
+LTTng 0.222 supports kernel 2.6.34.4. It includes a lttng splice actor +adjustment to match a splice.c change in 2.6.34.2 which changed the checks for +seekable files.
+LTTV 0.12.35 fixes a problem introduced in 0.12.34, fixing the problem initially +fixed by 0.12.34 in the "correct" way; without unwanted side-effects. LTTV +0.12.34 had problems calling hooks for some events.
+LTTng 0.223 supports kernel 2.6.35.2.