2.10

LTTng-modules - Bug #938: Enabling two events with same name but not the same event type cause no warning and does not behave as expected

LTTng-tools - Bug #1081: lttng-create behaviour does not match its command-line specification

LTTng-tools - Bug #1092: Channel switch timers don't seem to be honored

Bug #1097: Codename for LTTng 2.10

LTTng-tools - Bug #1099: Channel monitoring timer is not saved by the lttng save command

LTTng-tools - Bug #1101: Channel position sampling should be disabled for lttng-modules pre-2.10

LTTng-tools - Bug #1102: Trigger conditions are not evaluated on subscription

LTTng-tools - Bug #1103: lttng-sessiond reports an unknown kernel channel being removed on shutdown

LTTng-tools - Bug #1104: lttng-sessiond's new notification subsystem uses eventfd() which is only available since Linux 2.6.22

LTTng-tools - Bug #1105: The trigger API should warn the client when an unsupported condition is being used

LTTng-modules - Bug #1111: Sleeping function called from invalid context

LTTng-tools - Bug #1114: Possible invalid discarded events count

LTTng-tools - Bug #1119: Channel blocking timer is not saved (and loaded) by the lttng save command

LTTng-tools - Bug #1125: Functions added to lttng-ctl as part of the 2.10 release cycle are undocumented

LTTng-UST - Bug #1171: lttng_ust_delete_fd_from_tracker: Assertion failure

LTTng-UST - Bug #1176: Cannot build LTTng-ust from source with JUL support

LTTng-tools - Bug #1178: error reported in multilib session tracing scenario

LTTng-UST - Bug #1198: Failed to build with asciidoc 8.6.10, Ubuntu18.04

LTTng-UST - Bug #1199: close() implementation of ust-fd is not async-signal-safe causing child processes to hang forever after fork()

LTTng-UST - Bug #1200: Preloading both ust-fd and ust-fork will endup in deadlock situation after fork()

LTTng-UST - Bug #1201: ust_fd close() causes deadlock for any multithreaded application

LTTng-UST - Bug #1213: Cannot print trace under chroot

LTTng