Project

General

Profile

Issues

Filters

Apply Clear

# Project Tracker Status Priority Subject Assignee Target version
934 LTTng Bug Confirmed Normal Session in snapshot mode does not indicate a path when listed LTTng - 2.6 Actions
1219 LTTng-tools Bug New Normal regression/tools/clear intermitent failure on powerpc Jérémie Galarneau LTTng - 2.12 Actions
1217 LTTng-tools Bug New Normal regression/tools/live intermitent failure on yocto with 2.11 Jonathan Rajotte Julien LTTng - 2.11 Actions
1180 LTTng-tools Feature New Normal SDT tracing does not work when the probes are compiled with semaphores Francis Deslauriers LTTng - 2.11 Actions
1177 LTTng Bug Confirmed Normal Document --pidfile of lttng-sessiond executable Jonathan Rajotte Julien LTTng - 2.11 Actions
1159 LTTng-tools Bug Feedback Low Missing documentation: before Linux 4.17, suspending the system while tracing is active can result in incorrect event record timestamps Philippe Proulx LTTng - 2.11 Actions
1158 LTTng-tools Bug New Normal lttng-create(1) man page: it is not documented that --shm-path only applies to the user space domain Philippe Proulx LTTng - 2.11 Actions
1137 LTTng-tools Feature Confirmed Normal Version handshake for lttng-consumerd and lttng-sessiond LTTng - 2.11 Actions
1133 LTTng-tools Feature New Normal Metadata regeneration does not have to be "destructive" LTTng - 2.11 Actions
749 LTTng-tools Feature Confirmed Normal lttng list <session> should list the contexts added to each channel LTTng - 2.11 Actions
1213 LTTng-UST Bug Feedback Normal Cannot print trace under chroot LTTng - 2.10 Actions
1198 LTTng-UST Bug New High Failed to build with asciidoc 8.6.10, Ubuntu18.04 LTTng - 2.10 Actions
1178 LTTng-tools Bug Feedback Normal error reported in multilib session tracing scenario LTTng - 2.10 Actions
1176 LTTng-UST Bug New Normal Cannot build LTTng-ust from source with JUL support LTTng - 2.10 Actions
1114 LTTng-tools Bug New Normal Possible invalid discarded events count LTTng - 2.10 Actions
1105 LTTng-tools Bug New Normal The trigger API should warn the client when an unsupported condition is being used LTTng - 2.10 Actions
1102 LTTng-tools Bug In Progress Normal Trigger conditions are not evaluated on subscription LTTng - 2.10 Actions
1092 LTTng-tools Bug New Normal Channel switch timers don't seem to be honored LTTng - 2.10 Actions
938 LTTng-modules Bug Confirmed Normal Enabling two events with same name but not the same event type cause no warning and does not behave as expected LTTng - 2.10 Actions
(226-244/244) Per page: 25, 50, 100

Also available in: Atom CSV PDF