X-Git-Url: http://git.liburcu.org/?a=blobdiff_plain;f=doc%2Fdeveloper%2Flttng-lttv-compatibility.html;h=4a839ef854c1d444a35771f2bffa7837a6cd11b3;hb=b72cc11e887a1f8410b93de4c5da7c18c6ca74ae;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..4a839ef8 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,12 @@ powerpc64, s390, sparc, sparc64.
0.218
0.219
0.220
+0.221
+0.222
+0.223
+0.224
+0.225
+0.226
0.76
@@ -3877,6 +3885,9 @@ obsolete
2.6.33.3
2.6.33.4
2.6.34
+2.6.34.4
+2.6.35.2
+2.6.35.4
LTTng 0.191, LTTV 0.12.30 coming with trace format 2.6 revert to the pre-2.4 @@ -3956,6 +3967,74 @@ 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.
+LTTng 0.224 fixes socket instrumentation in git tree: the patch hunk management +differs between quilt and git, so only the git tree showed this problem.
+LTTng 0.225 supports kernel 2.6.35.4, updates generic alignment patch.
+LTTng 0.226 is a simple cleanup: it removes the unused psrwlock patches.
+ + + + +x86, alpha, arm26, avr32, cris, frv, h8300, m32r, m68knommu, parisc, sh, sh64, +um, v850, xtensa.
+arm, i686, ia64, m68k, mips, mipsel, x86_64, powerpc 405, +powerpc64, s390, sparc, sparc64.
+ + + + + +0.12.30
+...
+0.12.35
+ + +0.227
+0.228
+0.229
+ + +0.76
+...
+0.87
+ + +0.16
+0.17
+0.18
+ + +0.6
+ + +obsolete
+ + +2.6
+ + +2.6.35.4
+ + +LTTng 0.227 re-introduces the lttng-modules package, which splits the kernel +patches from the LTTng tracer. It matches lttng-modules 0.16.
+LTTng 0.228 and lttng-modules 0.17 removes the now unneeded patches from the +lttng kernel tree.
+LTTng 0.229 and lttng-modules 0.18 re-insert a few missing patches in the kernel +patchset and fixes a circular module dependency in lttng-modules.