2.10 open 2.10 77% 22 issues (17 closed — 5 open) Related issues Bug #1097: Codename for LTTng 2.10 Actions LTTng-modules - Bug #938: Enabling two events with same name but not the same event type cause no warning and does not behave as expected Actions LTTng-modules - Bug #1111: Sleeping function called from invalid context Actions LTTng-tools - Bug #1081: lttng-create behaviour does not match its command-line specification Actions LTTng-tools - Bug #1092: Channel switch timers don't seem to be honored Actions LTTng-tools - Bug #1099: Channel monitoring timer is not saved by the lttng save command Actions LTTng-tools - Bug #1101: Channel position sampling should be disabled for lttng-modules pre-2.10 Actions LTTng-tools - Bug #1102: Trigger conditions are not evaluated on subscription Actions LTTng-tools - Bug #1103: lttng-sessiond reports an unknown kernel channel being removed on shutdown Actions LTTng-tools - Bug #1104: lttng-sessiond's new notification subsystem uses eventfd() which is only available since Linux 2.6.22 Actions LTTng-tools - Bug #1105: The trigger API should warn the client when an unsupported condition is being used Actions LTTng-tools - Bug #1114: Possible invalid discarded events count Actions LTTng-tools - Bug #1119: Channel blocking timer is not saved (and loaded) by the lttng save command Actions LTTng-tools - Bug #1125: Functions added to lttng-ctl as part of the 2.10 release cycle are undocumented Actions LTTng-tools - Bug #1178: error reported in multilib session tracing scenario Actions LTTng-UST - Bug #1171: lttng_ust_delete_fd_from_tracker: Assertion failure Actions LTTng-UST - Bug #1176: Cannot build LTTng-ust from source with JUL support Actions LTTng-UST - Bug #1198: Failed to build with asciidoc 8.6.10, Ubuntu18.04 Actions LTTng-UST - Bug #1199: close() implementation of ust-fd is not async-signal-safe causing child processes to hang forever after fork() Actions LTTng-UST - Bug #1200: Preloading both ust-fd and ust-fork will endup in deadlock situation after fork() Actions LTTng-UST - Bug #1201: ust_fd close() causes deadlock for any multithreaded application Actions LTTng-UST - Bug #1213: Cannot print trace under chroot Actions
2.11 open 2.11 46% 13 issues (6 closed — 7 open) Related issues Bug #1177: Document --pidfile of lttng-sessiond executable Actions LTTng-modules - Bug #1253: Compilation bugs under CentOS 8.1 kernel 4.18.0-147.5.1.el8_1.x86_64 Actions LTTng-modules - Bug #1344: lttng-modules v2.11 package fails to build with a custom Linux Kernel build using Buildroot Actions LTTng-tools - Bug #1158: lttng-create(1) man page: it is not documented that --shm-path only applies to the user space domain Actions LTTng-tools - Bug #1159: Missing documentation: before Linux 4.17, suspending the system while tracing is active can result in incorrect event record timestamps Actions LTTng-tools - Bug #1170: Using the --output flag with the new dynamic tracing feature in 2.11 causes the trace to be lost / no output produced Actions LTTng-tools - Bug #1217: regression/tools/live intermitent failure on yocto with 2.11 Actions LTTng-tools - Bug #1241: lttng_destroy_session_no_wait always return LTTNG_ERR_INVALID in LTTng-2.11 and won't destroy the session Actions LTTng-tools - Feature #749: lttng list <session> should list the contexts added to each channel Actions LTTng-tools - Feature #1133: Metadata regeneration does not have to be "destructive" Actions LTTng-tools - Feature #1137: Version handshake for lttng-consumerd and lttng-sessiond Actions LTTng-tools - Feature #1180: SDT tracing does not work when the probes are compiled with semaphores Actions LTTng-UST - Bug #1204: Application is aborted immediately with coredump if ust-fd is preload Actions
2.12 open 2.12 40% 5 issues (2 closed — 3 open) Related issues Bug #1305: Kernel test hang Actions LTTng-tools - Bug #1219: regression/tools/clear intermitent failure on powerpc Actions LTTng-tools - Bug #1266: 2.12 fails to compile with C++ code when using session clear feature Actions LTTng-tools - Bug #1297: 2.12.3: test suite is failing Actions LTTng-tools - Bug #1318: lttng-tools configured with --with-consumerd32-libdir --with-consumerd32-bin does not start a 32bit consumerd on launch Actions
2.13 open 2.13 83% 6 issues (5 closed — 1 open) Related issues LTTng-modules - Bug #1358: Failed to deploy lttng modules on NVIDIA jetson device Actions LTTng-UST - Bug #1306: Detect probe providers built against old lttng-ust (.so.0) in lttng-ust .so.1 Actions LTTng-UST - Bug #1309: Add tests for compat API 0 Actions LTTng-UST - Bug #1310: Update man pages for API 1 Actions LTTng-UST - Bug #1332: LTTng-UST requires glibc >= 2.16 to build Actions LTTng-UST - Bug #1355: Pointers are rejected by integer element compile time assertion for array and sequence Actions
2.14 open 2.14 20% 5 issues (1 closed — 4 open) Related issues Feature #1347: Codename for 2.14 Actions LTTng-modules - Bug #1363: Build against 6.0.7 fails due to implicit declaration of lttng_kvm_x86_get_segment_base Actions LTTng-tools - Bug #833: memcpy of non-packed struct into packed struct (possible layout mismatch) Actions LTTng-tools - Bug #1128: Contexts can be added multiple times to a kernel channel Actions LTTng-tools - Bug #1362: Listing a trigger with an event rule matches condition with a uprobe on an elf symbol crashes Actions
2.9 open 2.9 41% 36 issues (14 closed — 22 open) Related issues Bug #1023: Error message on enabling event/all event for -j/-l/-p Actions Bug #1034: KPROBE & KREPROBE support for saved/loaded sessions is not working Actions Bug #1056: Codename for LTTng 2.9 Actions Bug #1183: LTTng-UST and modules ring buffers timestamp_end value may not include last events in the packet (LTTng 2.2+) Actions Feature #968: lttng-modules kernel and user callstack context Actions Feature #990: Additional make check targets Actions LTTng-modules - Bug #1029: lttng load handles out-of-memory badly Actions LTTng-modules - Bug #1032: LTTng session daemon may hang under certain circumstances Actions LTTng-modules - Bug #1090: LTTng modules not working after installing stable PPA Actions LTTng-tools - Bug #752: Output paths need better handling than truncation Actions LTTng-tools - Bug #897: Some commands are not gracefully handling the absence of a session daemon Actions LTTng-tools - Bug #901: Some liblttng-ctl don't return LTTNG_OK on success Actions LTTng-tools - Bug #919: “lttng track” list pid in order when listing with ust. Kernel is alright. look for sorting and output Actions LTTng-tools - Bug #928: It is possible to specify multiple positional arguments in enable-event command with no effect Actions LTTng-tools - Bug #930: "Non-default channel exists within session" when enabling UST/kernel and agent events Actions LTTng-tools - Bug #987: Incomplete string comparison pattern Actions LTTng-tools - Bug #994: Configured metadata data channel not listed for UST domain Actions LTTng-tools - Bug #995: cannot enable discard-mode channels in snapshot sessions Actions LTTng-tools - Bug #1024: lttng save [--all] issues misleading message when there are no sessions to save Actions LTTng-tools - Bug #1025: lttng load [--all] issues misleading message when there are no sessions to load Actions LTTng-tools - Bug #1026: lttng create should recover from a bad output option more gracefully Actions LTTng-tools - Bug #1033: lttng load does not preserve event or channel ordering Actions LTTng-tools - Bug #1068: lttng-ctl: lttng_load_session_attr_get_override_ctrl_url() returns NULL when the destination override is set using lttng_load_session_attr_set_override_url() Actions LTTng-tools - Bug #1071: lttng-mi XSD does not take new 2.9 override options into account Actions LTTng-tools - Bug #1078: lttng enable-event throws the error "UST create channel failed" Actions LTTng-tools - Bug #1182: relayd mishandles channels configured with tracefile-count == 0 and tracefile-size != 0 Actions LTTng-tools - Feature #808: Add --all to start command. Actions LTTng-tools - Feature #922: Expose cpu_id as a context field in lttng-tools (add-context) Actions LTTng-tools - Feature #932: LTTng client error code semantics are ill-defined Actions LTTng-tools - Feature #961: Add additional criteria to disable-event Actions LTTng-tools - Feature #985: Print *real* total size of buffers on channel listing Actions LTTng-UST - Bug #626: assertion in libust cause application to quit Actions LTTng-UST - Bug #1027: Python Tracing Actions LTTng-UST - Bug #1042: Error during make on a clean system Actions LTTng-UST - Bug #1064: Deadlock while dlopen-ing a provider Actions LTTng-UST - Bug #1089: lttng-ust examples build fail when invoking make more than once Actions
Babeltrace - Babeltrace - 2.1 open 22% 9 issues (2 closed — 7 open) Related issues Babeltrace - Bug #1227: cli: Error when using --clock-cycles and -c sink.text.pretty at the same time Actions Babeltrace - Bug #1229: flt.utils.trimmer: with no date, beginning time cannot be greater than end time Actions Babeltrace - Bug #1230: flt.utils.trimmer: local time can be nonexistent or ambiguous with DST Actions Babeltrace - Bug #1232: src.ctf.fs: variant option names without their tag equivalent are accepted, but the decoding process asserts Actions Babeltrace - Bug #1235: configure.ac: using python-config --libs instead of python-config --ldflags Actions Babeltrace - Bug #1237: Built-in plugins are not relinked to the application after a modification Actions Babeltrace - Bug #1289: docs: document that the "notext" flag is required to build out of tree plug-ins when linking with LLVM's ld Actions Babeltrace - Feature #1233: Python: Add __str__ to Message types, and perhaps other types Actions Babeltrace - Feature #1300: babeltrace2 lacks knowledge of bitwise enum produced by lttng-modules Actions
Babeltrace - Babeltrace - stable 1.x open 50% 2 issues (1 closed — 1 open) Related issues Babeltrace - Bug #1274: "[error] Event id ____ is outside range." when reading a trace Actions Babeltrace - Bug #1350: Babeltrace failes at a negative clock `offset` Actions
Babeltrace - Babeltrace - stable 2.0 open 16% 35 issues (5 closed — 30 open) Related issues Babeltrace - Bug #1221: Babeltrace 2 sometimes fail on live trace with lttng-clear feature Actions Babeltrace - Bug #1222: src.ctf.lttng-live: reading two per-pid traces does not emit messages Actions Babeltrace - Bug #1223: Check for cmp and diff in configure Actions Babeltrace - Bug #1224: Crash while reading a live per-pid trace Actions Babeltrace - Bug #1225: src.ctf.lttng-live: `sessions` query error reporting Actions Babeltrace - Bug #1228: calling seek to beginning after seek to ns from origin Actions Babeltrace - Bug #1231: AddressSanitizer detects an global buffer overflow when we iterate over plugin .so descriptors Actions Babeltrace - Bug #1234: src.text.dmesg: some kernel ring buffer lines can be wrongly sorted by time, leading to a muxer error Actions Babeltrace - Bug #1236: SIGTRAP in glib found during fuzzing Actions Babeltrace - Bug #1240: Can't write plugins solely with `--enable-python-plugins` Actions Babeltrace - Bug #1254: Trace with non-monotonic clocks make babeltrace2 abort Actions Babeltrace - Bug #1255: Babeltrace2 fails to process trace with begin timestamp of second packet smaller than begin timestamp of first packet Actions Babeltrace - Bug #1258: Segmentation fault when running with --debug Actions Babeltrace - Bug #1259: improved to description/usecases for streams and packets. Actions Babeltrace - Bug #1260: Babeltrace 2 refuses a trace when a previous packet has an end time > begin of the next packet Actions Babeltrace - Bug #1272: Test failures on Alpine Linux re: python bindings Actions Babeltrace - Bug #1277: The `ctf` plugin does not support a negative TSDL clock class `offset` attribute Actions Babeltrace - Bug #1278: "Graph failed to complete successfully" error Actions Babeltrace - Bug #1279: Bus error with custom source, muxer and sink.ctf.fs Actions Babeltrace - Bug #1282: `src.ctf.fs` accepts the same input twice Actions Babeltrace - Bug #1293: Use after free in sink.ctf.fs finalize Actions Babeltrace - Bug #1295: Copy-pasto in bt_value_map_borrow_entry_value doc Actions Babeltrace - Bug #1299: babeltrace2 re-uses prior event string rather than expected empty string Actions Babeltrace - Bug #1319: Assert in emit_inactivity_message Actions Babeltrace - Bug #1321: Segfault in bfcr_unsigned_int_cb() Actions Babeltrace - Bug #1322: Assert in ctf_msg_iter_destroy() Actions Babeltrace - Bug #1333: Crash on invalid argument sequence Actions Babeltrace - Bug #1334: Python component class memory leak Actions Babeltrace - Bug #1338: Crash when specifying convert command with custom python plug-in Actions Babeltrace - Bug #1346: sink.ctf.fs: Assertion failure while encoding length FC of dynamic array FC embedded within a static array FC Actions Babeltrace - Bug #1348: Assertion failure when passing `smalltrace` CTF test trace twice to convert command Actions Babeltrace - Bug #1351: Babeltrace2 failes at a negative clock `offset` Actions Babeltrace - Bug #1364: CTF: Mismatching variant and tag selector and field names causes a crash Actions Babeltrace - Feature #1226: Allow making graph execution more "event-based" Actions Babeltrace - Feature #1336: Improve usability of error messages Actions
Refactoring open Possible refactoring 0% 3 issues (0 closed — 3 open) Related issues LTTng-tools - Bug #1124: lttng-sessiond saves empty domain stubs Actions LTTng-tools - Feature #1126: Analyse and refactor interaction based on pipe and converge toward a solution that will result in a convergence in code Actions LTTng-tools - Feature #1127: regression/tool/filtering use local gen-ust-event instead of tests/utils Actions
Wishlist open Nice to have 11% 49 issues (2 closed — 47 open) Related issues Bug #1060: Document the extra reading subbuffer always allocated Actions Feature #211: Environment vars Actions LTTng-modules - Feature #950: Exclude specific kernel events when enabling all of them Actions LTTng-modules - Feature #962: add x86 exceptions.h and irq_vectors.h instrumentation (and mpx.h) Actions LTTng-modules - Feature #963: Implement user-space stack dump context Actions LTTng-modules - Feature #964: Implement support for persistent memory buffers Actions LTTng-modules - Feature #1067: Update writeback instrumentation for newer kernels Actions LTTng-tools - Bug #409: Detection of pipe close with POLLHUP poll(3) event Actions LTTng-tools - Bug #531: Event name scoping seems ill-defined Actions LTTng-tools - Bug #561: Under certain conditions, a user-space trace may overwrite itself Actions LTTng-tools - Bug #592: Potential trace process subdirectory name collision with PID namespaces Actions LTTng-tools - Bug #653: LTTng memory allocation failure goes unreported Actions LTTng-tools - Bug #720: Disambiguating fully qualified event names, timestamp-sensitive metadata Actions LTTng-tools - Bug #797: Add more test for epoll in configure Actions LTTng-tools - Bug #822: bash-completion sometimes completes too much Actions LTTng-tools - Bug #911: lttng save and MI should both point to their XSDs Actions LTTng-tools - Feature #15: LTTng simple trace Actions LTTng-tools - Feature #35: Remote administration Actions LTTng-tools - Feature #77: Create developper documentation for the LTTng "control" API Actions LTTng-tools - Feature #106: Missing context information in list command Actions LTTng-tools - Feature #137: No more tracing possible after consumerD dies (via kill command) Actions LTTng-tools - Feature #193: Find a more intelligent heuristics for the FD reservation Actions LTTng-tools - Feature #270: Be able to choose session by number in lttng list command Actions LTTng-tools - Feature #286: Add a --logfile option (or log through Syslog) Actions LTTng-tools - Feature #445: lttng enable-event and event redefinition: user feedback can be misleading Actions LTTng-tools - Feature #555: add-context --help lists perf fields even when the machine has no generic registers at all Actions LTTng-tools - Feature #558: Apply fd accounting technique from sessiond to consumerd Actions LTTng-tools - Feature #566: User-space data buffering schemes and the lttng user interface Actions LTTng-tools - Feature #573: Destroy an internal domain session on command error if created in that code flow Actions LTTng-tools - Feature #599: second snapshot not to gather data from the previous snapshot (no repeated events) Actions LTTng-tools - Feature #632: Several commands could benefit from an "all" option Actions LTTng-tools - Feature #750: lttng add-context --channel should accept a list of channels Actions LTTng-tools - Feature #766: Trace file rotation to consider older sessions in same tree Actions LTTng-tools - Feature #821: trace session name in the metadata Actions LTTng-tools - Feature #883: consumerd: Automatic reconnect to relayd Actions LTTng-tools - Feature #894: Cannot enable channel for JUL (-j) or Log4j (-l) domains Actions LTTng-tools - Feature #960: Add a -m /--matching argument to enable-event Actions LTTng-tools - Feature #984: Session path in LTTng profiles should not contain date and time Actions LTTng-tools - Feature #986: Warn when unreasonably short timer values are used Actions LTTng-tools - Feature #1066: Add option for lttng-destroy to delete the trace folder Actions LTTng-UST - Feature #38: Automatic stdout/stderr redirection Actions LTTng-UST - Feature #39: Auto-instrumentation of function entries and exits Actions LTTng-UST - Feature #51: lttng-gen-tp: add python module output Actions LTTng-UST - Feature #65: Helper script to generate the tracepoint shared library Actions LTTng-UST - Feature #395: Enable channel after start session Actions LTTng-UST - Feature #440: Tracepoint Documentation Actions LTTng-UST - Feature #508: arrays of floats are stored and/or displayed as arrays of ints Actions LTTng-UST - Feature #965: Implement UST statedump Actions LTTng-UST - Feature #1100: Add (possibly symbolic) event whenever blocking occurs due to excessive events Actions