Project

General

Profile

2.7

closed

2.7

100%

32 issues   (32 closed — 0 open)

Issues by
Bug

29/29
Feature

3/3
Related issues
LTTng-tools - Bug #780: Security: getenv() should not be used if daemon are in setuid mode Actions
LTTng-tools - Bug #847: Enabling system calls returns code 35 instead of 0 Actions
LTTng-tools - Bug #859: lttng client should not launch a session daemon unless required Actions
LTTng-UST - Bug #870: Python agent hang on teardown Actions
LTTng-tools - Bug #878: lttng-sessiond cannot unload lttng-modules when live session exists Actions
LTTng-tools - Bug #879: Lttng list shows max uint as live interval Actions
LTTng-modules - Bug #889: lttng-modules won't build - Ubuntu 14.04 - kernel 3.16.0-38 Actions
LTTng-tools - Bug #893: lttng-sessiond: buffer-registry.c:55: ht_match_reg_uid: Assertion `_key' failed. Actions
LTTng-tools - Bug #898: Enabling the tracking of a PID twice should provide a clearer error Actions
LTTng-tools - Bug #904: lttng enable-event –help and lttng disable-event –help should specify all domains at the top Actions
LTTng-tools - Bug #906: Enabling events in two agent domains corrupts the model Actions
LTTng-tools - Bug #908: Invalid free in list_ust_events Actions
LTTng-tools - Bug #909: lttng enable-event -p -a --exclude something hangs Actions
LTTng-tools - Bug #910: lttng enable-event -p/-l-/-j does not report a valid channel name Actions
LTTng-tools - Bug #913: Issuing both --loglevel and --loglevel-only for the same event and same level does not work Actions
Bug #914: lttng: Trace is going on even though event has been disabled Actions
LTTng-tools - Bug #915: Support symlinks for ltttng-crash Actions
LTTng-tools - Bug #917: Add track/untrack section in lttng(1) man page Actions
LTTng-tools - Bug #918: Untrack on an untracked pid should return an error Actions
LTTng-tools - Bug #924: Check for listing/mi/save/restore of filter on kernel domain Actions
LTTng-tools - Bug #925: Disabling a kernel event disables all kernel events Actions
LTTng-modules - Bug #926: Kernel dynamic function/probe tracing does not work Actions
LTTng-tools - Bug #927: Multiple domain options are allowed in commands where it should not Actions
LTTng-tools - Bug #929: Can only disable one event amongst many agent events sharing the same name Actions
LTTng-tools - Bug #931: Untracking a userspace pid which is not tracked results in an invalid parameter error Actions
LTTng-tools - Bug #936: Disable all event ust Actions
LTTng-tools - Bug #942: Listing a session's kernel events after enabling a syscall does not produce the same output before/after tracing is started. Actions
LTTng-modules - Bug #943: All events are filtered-out when using a wildcard in a filter's criterion Actions
LTTng-modules - Bug #947: Event address fields should be hexadecimal (base 16) Actions
LTTng-tools - Feature #916: Add tests for shm_path Actions
LTTng-tools - Feature #920: add tests for lttng-modules wildcards Actions
LTTng-tools - Feature #921: add tests for lttng-modules filter Actions

Also available in: TXT