Project

General

Profile

2.8

closed

2.8

100%

39 issues   (39 closed — 0 open)

Issues by
Bug

29/29
Feature

10/10
Related issues
LTTng-tools - Bug #725: babeltrace of flight recorder trace complains about spurious event losses Actions
LTTng-tools - Bug #896: lttng load prints that "All sessions were loaded successfully" even when no sessions are available Actions
LTTng-tools - Bug #899: Automatically-started lttng-sessiond does not like return code 2. Actions
LTTng-tools - Bug #905: Invalid flag proposed in error from enable/disable context Actions
LTTng-tools - Bug #912: Standalone versioning for mi api (xml) Actions
LTTng-UST - Bug #933: Cannot list Java events Actions
LTTng-tools - Bug #939: Test lttng-modules clock plugin Actions
Bug #948: Codename for the LTTng 2.8 release Actions
LTTng-tools - Bug #949: error reporting when kernel tracing not available because of a version mismatch between tools and modules Actions
LTTng-tools - Bug #951: Make distclean fail Actions
LTTng-tools - Bug #956: --enable-lttng-ust should be --with/--without Actions
LTTng-tools - Bug #958: lttng-ust, lttng-tools sensitive to /usr/local/lib Actions
LTTng-tools - Bug #959: Event status incorrect after load Actions
LTTng-tools - Bug #970: snapshot written in 2 folders if it takes more than 1 second to record Actions
LTTng-tools - Bug #973: Failure when loading saved live session Actions
LTTng-tools - Bug #976: lttng-sessiond spams logs when an invalid UST context is added to a channel Actions
LTTng-tools - Bug #977: Static build is broken because of ust-dl test Actions
LTTng-tools - Bug #988: lttng -q option not functional Actions
LTTng-tools - Bug #998: UST and Java/Python log levels are not ordered the same way Actions
LTTng-tools - Bug #1001: The configure script does not check liburcu's binary library Actions
LTTng-tools - Bug #1002: lttng snapshot on an empty tracing session results in an unknown error with --mi=xml Actions
LTTng-tools - Bug #1003: Passing an unexpected argument to "lttng metadata" should result in an error. Actions
LTTng-tools - Bug #1006: Enabling an application context (both JUL and log4j) results in a misleading confirmation message Actions
LTTng-tools - Bug #1011: lttng without any argument does not show help/usage Actions
LTTng-tools - Bug #1012: Snapshot record results in warning if there are no events in one of the domains Actions
LTTng-tools - Bug #1013: Loading a session prints an error message and exits with non-zero status, but the load is successful Actions
LTTng-tools - Bug #1021: README.md: missing Fedora devel packages Actions
LTTng-UST - Bug #1035: lttng-ust 2.8 does not dump base address of lib dependencies of dlopen'd libs Actions
LTTng-modules - Bug #1098: LTTng-modules-stable-2.8-2.8.2-e840206 does not compile under Ubuntu 14.04.5 Actions
LTTng-tools - Feature #334: Display configured filter Actions
LTTng-UST - Feature #474: Make lttng-ust aware of shared object base addresses Actions
LTTng-tools - Feature #630: 'lttng list session_name' should list the filters attached to the events Actions
LTTng-tools - Feature #836: List of events (lttng list) presents usability problems Actions
LTTng-tools - Feature #839: Split manpage of lttng command Actions
LTTng-tools - Feature #853: Live session is listed by relayd after the session has been destroyed Actions
LTTng-tools - Feature #923: Document cpu_id context Actions
Feature #954: Allow regenerating the LTTng-UST and LTTng-modules metadata after NTP major adjustment Actions
Feature #955: Expose buffer overwritten information in LTTng-UST and LTTng-modules Actions
Feature #966: Merge Java early filtering feature Actions

Also available in: TXT