LTTng - 2.10 open 2.10 77% 22 issues (17 closed — 5 open) Related issues Bug #1081: lttng-create behaviour does not match its command-line specification Actions Bug #1092: Channel switch timers don't seem to be honored Actions Bug #1099: Channel monitoring timer is not saved by the lttng save command Actions Bug #1101: Channel position sampling should be disabled for lttng-modules pre-2.10 Actions Bug #1102: Trigger conditions are not evaluated on subscription Actions Bug #1103: lttng-sessiond reports an unknown kernel channel being removed on shutdown Actions Bug #1104: lttng-sessiond's new notification subsystem uses eventfd() which is only available since Linux 2.6.22 Actions Bug #1105: The trigger API should warn the client when an unsupported condition is being used Actions Bug #1114: Possible invalid discarded events count Actions Bug #1119: Channel blocking timer is not saved (and loaded) by the lttng save command Actions Bug #1125: Functions added to lttng-ctl as part of the 2.10 release cycle are undocumented Actions Bug #1178: error reported in multilib session tracing scenario Actions
LTTng - 2.11 open 2.11 46% 13 issues (6 closed — 7 open) Related issues Bug #1158: lttng-create(1) man page: it is not documented that --shm-path only applies to the user space domain Actions Bug #1159: Missing documentation: before Linux 4.17, suspending the system while tracing is active can result in incorrect event record timestamps Actions 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 Bug #1217: regression/tools/live intermitent failure on yocto with 2.11 Actions Bug #1241: lttng_destroy_session_no_wait always return LTTNG_ERR_INVALID in LTTng-2.11 and won't destroy the session Actions Feature #749: lttng list <session> should list the contexts added to each channel Actions Feature #1133: Metadata regeneration does not have to be "destructive" Actions Feature #1137: Version handshake for lttng-consumerd and lttng-sessiond Actions Feature #1180: SDT tracing does not work when the probes are compiled with semaphores Actions
LTTng - 2.12 open 2.12 40% 5 issues (2 closed — 3 open) Related issues Bug #1219: regression/tools/clear intermitent failure on powerpc Actions Bug #1266: 2.12 fails to compile with C++ code when using session clear feature Actions Bug #1297: 2.12.3: test suite is failing Actions Bug #1318: lttng-tools configured with --with-consumerd32-libdir --with-consumerd32-bin does not start a 32bit consumerd on launch Actions
LTTng - 2.13 open 2.13 85% 7 issues (6 closed — 1 open) Related issues Bug #1411: Memory leak when relay daemon exits before application starts Actions
LTTng - 2.14 open 2.14 14% 7 issues (1 closed — 6 open) Related issues Bug #833: memcpy of non-packed struct into packed struct (possible layout mismatch) Actions Bug #1128: Contexts can be added multiple times to a kernel channel Actions Bug #1362: Listing a trigger with an event rule matches condition with a uprobe on an elf symbol crashes Actions
LTTng - 2.9 open 2.9 42% 35 issues (14 closed — 21 open) Related issues Bug #752: Output paths need better handling than truncation Actions Bug #897: Some commands are not gracefully handling the absence of a session daemon Actions Bug #919: “lttng track” list pid in order when listing with ust. Kernel is alright. look for sorting and output Actions Bug #928: It is possible to specify multiple positional arguments in enable-event command with no effect Actions Bug #930: "Non-default channel exists within session" when enabling UST/kernel and agent events Actions Bug #987: Incomplete string comparison pattern Actions Bug #994: Configured metadata data channel not listed for UST domain Actions Bug #995: cannot enable discard-mode channels in snapshot sessions Actions Bug #1024: lttng save [--all] issues misleading message when there are no sessions to save Actions Bug #1025: lttng load [--all] issues misleading message when there are no sessions to load Actions Bug #1026: lttng create should recover from a bad output option more gracefully Actions Bug #1033: lttng load does not preserve event or channel ordering Actions 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 Bug #1071: lttng-mi XSD does not take new 2.9 override options into account Actions Bug #1078: lttng enable-event throws the error "UST create channel failed" Actions Bug #1182: relayd mishandles channels configured with tracefile-count == 0 and tracefile-size != 0 Actions Feature #808: Add --all to start command. Actions Feature #922: Expose cpu_id as a context field in lttng-tools (add-context) Actions Feature #932: LTTng client error code semantics are ill-defined Actions Feature #961: Add additional criteria to disable-event Actions Feature #985: Print *real* total size of buffers on channel listing Actions
LTTng - Refactoring open Possible refactoring 0% 3 issues (0 closed — 3 open) Related issues Bug #1124: lttng-sessiond saves empty domain stubs Actions Feature #1126: Analyse and refactor interaction based on pipe and converge toward a solution that will result in a convergence in code Actions Feature #1127: regression/tool/filtering use local gen-ust-event instead of tests/utils Actions
LTTng - Wishlist open Nice to have 14% 53 issues (4 closed — 49 open) Related issues Bug #409: Detection of pipe close with POLLHUP poll(3) event Actions Bug #531: Event name scoping seems ill-defined Actions Bug #561: Under certain conditions, a user-space trace may overwrite itself Actions Bug #592: Potential trace process subdirectory name collision with PID namespaces Actions Bug #653: LTTng memory allocation failure goes unreported Actions Bug #720: Disambiguating fully qualified event names, timestamp-sensitive metadata Actions Bug #797: Add more test for epoll in configure Actions Bug #822: bash-completion sometimes completes too much Actions Bug #911: lttng save and MI should both point to their XSDs Actions Feature #15: LTTng simple trace Actions Feature #35: Remote administration Actions Feature #77: Create developper documentation for the LTTng "control" API Actions Feature #106: Missing context information in list command Actions Feature #137: No more tracing possible after consumerD dies (via kill command) Actions Feature #193: Find a more intelligent heuristics for the FD reservation Actions Feature #270: Be able to choose session by number in lttng list command Actions Feature #286: Add a --logfile option (or log through Syslog) Actions Feature #445: lttng enable-event and event redefinition: user feedback can be misleading Actions Feature #555: add-context --help lists perf fields even when the machine has no generic registers at all Actions Feature #558: Apply fd accounting technique from sessiond to consumerd Actions Feature #566: User-space data buffering schemes and the lttng user interface Actions Feature #573: Destroy an internal domain session on command error if created in that code flow Actions Feature #599: second snapshot not to gather data from the previous snapshot (no repeated events) Actions Feature #632: Several commands could benefit from an "all" option Actions Feature #750: lttng add-context --channel should accept a list of channels Actions Feature #766: Trace file rotation to consider older sessions in same tree Actions Feature #821: trace session name in the metadata Actions Feature #883: consumerd: Automatic reconnect to relayd Actions Feature #894: Cannot enable channel for JUL (-j) or Log4j (-l) domains Actions Feature #960: Add a -m /--matching argument to enable-event Actions Feature #984: Session path in LTTng profiles should not contain date and time Actions Feature #986: Warn when unreasonably short timer values are used Actions Feature #1066: Add option for lttng-destroy to delete the trace folder Actions Feature #1349: Add '--all' to lttng start Actions Feature #1391: Add 'enable-events' as a special argument to lttng-tools Actions