# 2.7

2.7

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