Hi,
Those are bugfix releases of LTTng-UST for the stable-2.9 and
stable-2.10 branches, as well as for the 2.11 branch, which is
currently in release candidate stage.
The fix "Fix: race between statedump and library destructor" takes
care of a crash happening in short-lived applications that use
- On Jan 25, 2019, at 3:15 PM, Michael Jeanson mjean...@efficios.com wrote:
> This will maintain buildtime compatibility with softwares like lttng-ust
> that used the prior undocumented multiflavor API.
>
> Signed-off-by: Michael Jeanson
> ---
> include/urcu/map/urcu-bp.h | 63
This will maintain buildtime compatibility with softwares like lttng-ust
that used the prior undocumented multiflavor API.
Signed-off-by: Michael Jeanson
---
include/urcu/map/urcu-bp.h | 63 ++
include/urcu/map/urcu-mb.h | 60
Please keep interaction on the mailing list.
On Fri, Jan 25, 2019 at 09:13:44AM +0530, Urmila R wrote:
> Hello
>
> To run session daemon as a root one should be member of tracing group
> is it mandatory ?
To perform kernel tracing, lttng-sessiond daemon MUST be run as root since
it must load
On Fri, Jan 25, 2019 at 4:05 AM Brian Rossa wrote:
>
> Francis,
>
> These are great suggestions, thanks!
>
>> #Third idea:
>> Do you know of tracef() [3] ? Using it, you can save any string to a
>> UST trace. As a first step, you could directly replace your calls to
>> spdlog by calls to tracef.
Francis,
These are great suggestions, thanks!
#Third idea:
> Do you know of tracef() [3] ? Using it, you can save any string to a
> UST trace. As a first step, you could directly replace your calls to
> spdlog by calls to tracef. It's an highly inefficient way of using
> LTTng, but it works (and
