Project

General

Profile

Issues

Filters

Apply Clear

# Project Tracker Status Priority Subject Assignee Target version
137 LTTng-tools Feature Confirmed Normal No more tracing possible after consumerD dies (via kill command) LTTng - Wishlist Actions
106 LTTng-tools Feature Confirmed Normal Missing context information in list command LTTng - Wishlist Actions
35 LTTng-tools Feature Confirmed Normal Remote administration LTTng - Wishlist Actions
1060 LTTng Bug Confirmed Low Document the extra reading subbuffer always allocated LTTng - Wishlist Actions
750 LTTng-tools Feature Confirmed Low lttng add-context --channel should accept a list of channels LTTng - Wishlist Actions
720 LTTng-tools Bug Confirmed Low Disambiguating fully qualified event names, timestamp-sensitive metadata LTTng - Wishlist Actions
653 LTTng-tools Bug Confirmed Low LTTng memory allocation failure goes unreported LTTng - Wishlist Actions
592 LTTng-tools Bug Confirmed Low Potential trace process subdirectory name collision with PID namespaces LTTng - Wishlist Actions
561 LTTng-tools Bug Confirmed Low Under certain conditions, a user-space trace may overwrite itself LTTng - Wishlist Actions
525 LTTng-UST Bug Confirmed Low new "notifications" from UST do not strictly respect LTTNG_UST_REGISTER_TIMEOUT Actions
409 LTTng-tools Bug Confirmed Low Detection of pipe close with POLLHUP poll(3) event LTTng - Wishlist Actions
270 LTTng-tools Feature Confirmed Low Be able to choose session by number in lttng list command LTTng - Wishlist Actions
77 LTTng-tools Feature Confirmed Low Create developper documentation for the LTTng "control" API LTTng - Wishlist Actions
15 LTTng-tools Feature Confirmed Low LTTng simple trace LTTng - Wishlist Actions
1352 LTTng-tools Bug Feedback Normal LTTng consumer daemon crashed with error: "Attempt to send invalid file descriptor to master (fd = -1)" Actions
1351 Babeltrace Bug Feedback Normal Babeltrace2 failes at a negative clock `offset` Babeltrace - Babeltrace - stable 2.0 Actions
1350 Babeltrace Bug Feedback Normal Babeltrace failes at a negative clock `offset` Babeltrace - Babeltrace - stable 1.x Actions
1331 LTTng-tools Bug Feedback Normal test_unix_socket fails for 64 bit arches on alpine linux but passes on 32bit arches Actions
1320 LTTng-UST Bug Feedback Normal Assert in lttng-ring-buffer-client.h:437: client_buffer_begin() Actions
1285 LTTng-UST Bug Feedback Normal about close file failed for lttng-ust module Actions
1278 Babeltrace Bug Feedback Normal "Graph failed to complete successfully" error Babeltrace - Babeltrace - stable 2.0 Actions
1215 LTTng-tools Bug Feedback Normal Failed to start lttng-sessiond process Actions
1208 LTTng Bug Feedback Normal 2.11 relayd in live mode attach window changed Actions
1195 LTTng Bug Feedback Normal Userspace tracing issue Actions
1168 Babeltrace Bug Feedback Normal CTF for a user-plugged clock assumes that "offset" is unsigned, but a negative value can happen and will result in unparsable metadata getting stored Actions
(76-100/254) Per page: 25, 50, 100

Also available in: Atom CSV PDF